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

[IwantToKeepAnon <iwanttokeepanon at yahoo dot com>]

"Christophe Beauregard"
<christophe.beauregard@sympatico.ca> writes:

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

If, when you "sign up" a new user, you check his user
id against the current user list.  If their id is
unique, then userId+recId _IS_ unique guaranteed! 
Across all devices.  I guess I am still a little in
the dark where the "multiuser" difficulty comes in.

Personally I would be more than willing to change my
user ID.  But muck with record IDs and IO the record 3
times ... not so much.

Despite all the "resistance" you are getting, it
sounds like a great project.  Which is probably why
this thread is so long!  Maybe you could put up a
couple of screen shots somewhere of what you are
developing.

L8r,
-- 
Rodney

=====
-- 
"A smile is the shortest distance between two people."
Victor Borge

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
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.