Re: [coldsync-hackers] Design logic of Sync conduits

["David A. Desrosiers" <hacker at gnu-designs dot com>]

> If Coldsync cannot uniquely identify it, there's not a lot I can do
> except write a large caveat.

	Heuristics are your friend here. Don't trust that any Palm device
will have anything you can guarantee will be on any other Palm device.
Just generate your own heuristic, from several pieces of data you know on
the Palm, and store that in the proper record in the Saved Preferences.prc
file (or in your own custom little database, if you prefer).

	Remember to also store this same heuristic "signature" on the
desktop as well, so a cleanly-wiped Palm will know that it should be
associated with a particular user on the desktop/networked machine, and
what records belong to that user at restore/install time.

> As far as I have read, this only appears to be a Handspring problem
> (interesting as I would quite like to get a Handspring Treo mobile phone
> at some point. Anyone out there have one?

	I have a Treo90 that Handspring sent me to get working with Linux
and pilot-link (apparently they use pilot-link internally, or at least
they used to, before Palm swallowed them up.. maybe they still do), but it
doesn't have the phone piece. A nice little unit, with phenomenal battery
life, and incredibly thin and light.

	What is it you'd like to know?

d.

This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.