Hi,

I agree with you Matthew. What do you think would be such operations,
that are needed for a more efficient synchronization?

I can think of only three:
1) Some kind of "mass-saving/updating" method would be needed. Because
when I sync after a long period of being offline, it's probable that a
lot has changed. And instead of making a single call for each of the
possibly hundred changed items, a single call with all changed items
within, would be a lot more efficient.

2) Something like "lastUpdate". The del.icio.us API has the "update"
call (http://del.icio.us/help/api/update) which returns the time the
last change happened on the server side. This would help save
unnecessary API calls. Some, if not a lot.

3) Going even further would be a call, that would return only the
added AND deleted items after a given point in time. I think this,
includes the "lastupdate" call somehow, and together with number 1)
would result in only a total of two calls being necessary for a
complete sync between local and remote.

What do you think?

Cheers

Benjamin


On 7/3/07, Matthew Turland <tobias382@...> wrote:
>
> A thought occurred to me today: I don't think there's any method of
> backing up one's bookmarks from Simpy without doing a full dump (which
> can tax the servers if you have a lot of bookmarks) or writing
> something to use the API to sychronize with a local copy bookmark by
> bookmark (which would tax the servers because of all the API calls
> that would be required). It would be easy enough to check for
> additions after a certain date, but this doesn't help for deletions
> without checking bookmarks individually. Otis, would it be possible to
> add something to Simpy to make synchronization with a local copy more
> feasible?
>
> Regards,
>
> Matthew Turland