![]() |
2006-06-20
, 16:05
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#2
|
![]() |
2006-06-20
, 16:44
|
Posts: 8 |
Thanked: 0 times |
Joined on Jun 2006
|
#3
|
![]() |
2006-06-21
, 11:10
|
|
Posts: 1,463 |
Thanked: 81 times |
Joined on Oct 2005
@ UK
|
#4
|
![]() |
2006-06-21
, 12:46
|
Posts: 227 |
Thanked: 51 times |
Joined on Feb 2006
|
#5
|
![]() |
2006-06-21
, 13:20
|
|
Posts: 1,463 |
Thanked: 81 times |
Joined on Oct 2005
@ UK
|
#6
|
![]() |
2006-06-21
, 13:46
|
Posts: 8 |
Thanked: 0 times |
Joined on Jun 2006
|
#7
|
![]() |
2006-06-21
, 15:07
|
Posts: 227 |
Thanked: 51 times |
Joined on Feb 2006
|
#8
|
Yeah, but file transfers doesn't mean manual syncing.
For example:
- Plug in 770, it becomes available as mass storage.
- Desktop sync application updates some file on MMC.
- User disconnects 770.
- Sync daemon on 770 detects new file on MMC and updates DB.
In fact, with an SQLite database on the MMC card, this could be updated directly by the desktop sync application.
The advantage of this approach over a custom protocol is that it's easier to make it available cross-platform, e.g. Windows, Linux, Mac OS X etc.
Obviously a more custom approach is necessary for the Bluetooth or wifi transfer (and harder for the user to setup, TBH).
![]() |
2006-06-21
, 15:23
|
|
Posts: 1,463 |
Thanked: 81 times |
Joined on Oct 2005
@ UK
|
#9
|
-R