Windows/Android synchronization Part 3
Content synchronization between 2 devices embedded with different platform is normally a process of making sure that a clustered of computer files in certain locations on both devices can be modified (including deleting, inserting, updating) via some rules. Basically those rules are some data proces...
Saved in:
Main Author: | |
---|---|
Other Authors: | |
Format: | Final Year Project |
Language: | English |
Published: |
2015
|
Subjects: | |
Online Access: | http://hdl.handle.net/10356/63095 |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Nanyang Technological University |
Language: | English |
id |
sg-ntu-dr.10356-63095 |
---|---|
record_format |
dspace |
spelling |
sg-ntu-dr.10356-630952023-03-03T20:59:41Z Windows/Android synchronization Part 3 Nie, Xiao Fan Rui School of Computer Engineering Parallel and Distributed Computing Centre DRNTU::Engineering::Computer science and engineering Content synchronization between 2 devices embedded with different platform is normally a process of making sure that a clustered of computer files in certain locations on both devices can be modified (including deleting, inserting, updating) via some rules. Basically those rules are some data processing algorithms and can help improve the efficiency of file comparisons and file transfer, thus satisfying the needs of users. Basically there are two ways to do file synchronization according to the direction of file transfer. The first way is called one-way file synchronization, sometimes we also name it mirroring. By using this way, entire files must be transferred from the source device to the target device at the first connection. All the comparisons are done at the source side and no files are going to be transferred from target device to source device. The second way is called two-way file synchronization. Comparisons are done at both sides and file transfer is bidirectional also. The purpose of both ways is to keep files on both devices identical. Nowadays file synchronization is mainly used to do backup for smartphones or content sharing among people at different physical locations. The application (or software) must be capable to efficiently recognize identical files and automatically do the file transfer for the rest. Compared to manually updating, it can save a lot of time and ensure accuracy if a large number of files needs to be transferred. Take Dropbox as an example, it is a file hosting service provide a cloud storage to help users synchronize their files. It is widely used among university students. It consists of four basic components, cloud, specified folder, personal could and a software on client side. It cannot work if one of the mentioned components is blocked. This is because the mechanism of Dropbox. Every single modification of files in the designated file of the user will be uploaded to the cloud side. Then other users can retrieve the updates from the cloud. It is a typical server to client architecture. So it is not that robust compared to a P2P. If the server is done client cannot do anything. The transfer speed is also not stable especially for mobile devices. Many people nowadays use both Android device and Windows device. In most of the time, they prefer to use their tablet or smartphone to read documents rather than a PC. So it is very necessary to build such an application that can automatically help people to transfer their desired files from PC to their mobile devices. So for this final year project, three of us will build an android-based application to automatically synchronize files between an Android device and a Windows device. Certain directories on both sides will be used do the synchronization. It is a P2P based application and can start synchronization at any time once the connection has been established between two devices. Also the device can recognize each other if both of them are under the same network. Since it is a peer-to-peer network, it can indeed perform more stable and higher speed transfer compared to a cloud-based network. Bachelor of Engineering (Computer Science) 2015-05-06T02:44:47Z 2015-05-06T02:44:47Z 2015 2015 Final Year Project (FYP) http://hdl.handle.net/10356/63095 en Nanyang Technological University 77 p. application/pdf |
institution |
Nanyang Technological University |
building |
NTU Library |
continent |
Asia |
country |
Singapore Singapore |
content_provider |
NTU Library |
collection |
DR-NTU |
language |
English |
topic |
DRNTU::Engineering::Computer science and engineering |
spellingShingle |
DRNTU::Engineering::Computer science and engineering Nie, Xiao Windows/Android synchronization Part 3 |
description |
Content synchronization between 2 devices embedded with different platform is normally a process of making sure that a clustered of computer files in certain locations on both devices can be modified (including deleting, inserting, updating) via some rules. Basically those rules are some data processing algorithms and can help improve the efficiency of file comparisons and file transfer, thus satisfying the needs of users. Basically there are two ways to do file synchronization according to the direction of file transfer. The first way is called one-way file synchronization, sometimes we also name it mirroring. By using this way, entire files must be transferred from the source device to the target device at the first connection. All the comparisons are done at the source side and no files are going to be transferred from target device to source device. The second way is called two-way file synchronization. Comparisons are done at both sides and file transfer is bidirectional also. The purpose of both ways is to keep files on both devices identical. Nowadays file synchronization is mainly used to do backup for smartphones or content sharing among people at different physical locations. The application (or software) must be capable to efficiently recognize identical files and automatically do the file transfer for the rest. Compared to manually updating, it can save a lot of time and ensure accuracy if a large number of files needs to be transferred. Take Dropbox as an example, it is a file hosting service provide a cloud storage to help users synchronize their files. It is widely used among university students. It consists of four basic components, cloud, specified folder, personal could and a software on client side. It cannot work if one of the mentioned components is blocked. This is because the mechanism of Dropbox. Every single modification of files in the designated file of the user will be uploaded to the cloud side. Then other users can retrieve the updates from the cloud. It is a typical server to client architecture. So it is not that robust compared to a P2P. If the server is done client cannot do anything. The transfer speed is also not stable especially for mobile devices. Many people nowadays use both Android device and Windows device. In most of the time, they prefer to use their tablet or smartphone to read documents rather than a PC. So it is very necessary to build such an application that can automatically help people to transfer their desired files from PC to their mobile devices. So for this final year project, three of us will build an android-based application to automatically synchronize files between an Android device and a Windows device. Certain directories on both sides will be used do the synchronization. It is a P2P based application and can start synchronization at any time once the connection has been established between two devices. Also the device can recognize each other if both of them are under the same network. Since it is a peer-to-peer network, it can indeed perform more stable and higher speed transfer compared to a cloud-based network. |
author2 |
Fan Rui |
author_facet |
Fan Rui Nie, Xiao |
format |
Final Year Project |
author |
Nie, Xiao |
author_sort |
Nie, Xiao |
title |
Windows/Android synchronization Part 3 |
title_short |
Windows/Android synchronization Part 3 |
title_full |
Windows/Android synchronization Part 3 |
title_fullStr |
Windows/Android synchronization Part 3 |
title_full_unstemmed |
Windows/Android synchronization Part 3 |
title_sort |
windows/android synchronization part 3 |
publishDate |
2015 |
url |
http://hdl.handle.net/10356/63095 |
_version_ |
1759855775712280576 |