On 12 Jan 2007, at 18:39, Rob wrote:
1) determining best way to handle local to network data sync.
I will be creating a UUID for each record so I'm not worried about
duplicate record ID's. What does concern me is how to determine
what records need to be synced. The only thing I can think of is to
have a "last modified" date field for server queries and an "to
update" Boolean field. When the sync command is called, the desktop
app would get a recordset based on the to update flag then generate
the sql to be sent to the server. The app would then request all
records updated after the last sync (local property).
Does this make sense or is there a better way to deal with
synchronizing data?
2) What would be the best way to handle network SQL strings. Send
the whole string over the network? Send the parameters and an SQL
identifier and have the php middleware assemble the SQL?
I don't think either would be that complicated but I am worried
about security.
OpenbaseSQL has synchronisation built-in, that way you don't have to
worry about how to implement it. If you want to have a look at what's
possible, have a look at Daylite, a Cocoa app using OpenbaseSQL.
Best regards
Peter De Berdt
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
