View Single Post
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#8
Originally Posted by aflegg
Yeah, but file transfers doesn't mean manual syncing.

For example:
  1. Plug in 770, it becomes available as mass storage.
  2. Desktop sync application updates some file on MMC.
  3. User disconnects 770.
  4. 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).
I agree with almost everything you say except I think a TCP/IP solution would be superior for a couple of reasons.

First TCP/IP is what provides the cross platform capability. Anything that can speak TCP can synchronize with the 770 PIM. With USB you are limited to only devices with USB host capability. If you wanted to sync your calendar with your phone, desktop, and 770 it becomes a multi step headache and conflict resolution becomes nearly impossible.

Next TCP/IP frees you from physical location. If you have a PIM server somewhere on the network you can pull / push changes to your info from anywhere in the world.

That is why I find SyncML attractive. I'm no expert in this stuff but I am pretty passionate about PIM stuff. I wish palm had not gone to hell in a handbasket with their platform.

David
__________________
David Smoot