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

[Christophe Beauregard <christophe dot beauregard at sympatico.ca>]

On Tuesday 24 February 2004 16:21, Marco van Beek wrote:
> > What about letting the Handheld assign its own record id and the Server
> > use its SQL ids, and then, for each Handheld, have a SQL table
> > containing (Database,hhID,sID), where Database is the name of the
> > Handheld database (DatebookDB, etc), hhID is the handheld record ID for
> > that database, and sID is the server record ID (which might be database
> > specific or it could be a global ID).

> Aha! - How about adding the Palm Serial Numbers numbers the table (so
> four fields, but only one table). This means I could look at using the
> user name properly as an ownership / responsibility field, as we could
> work by Palm Serial Number.

Sure... Although I understand PalmOS serial numbers are iffy.

The thing is, every new device is going to have to be "introduced" to the 
database server to have this mapping table created. You can use the userid, 
the serial number...

If you want to be really clever, you can create a small custom database on 
the Handheld containing some unique token (public ssh key, for example) and 
bypass the problematic Palm identification system entirely.

c.
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.