On 2007 Nov, 05, at 14:46, Toby Elliott wrote: > This sounds like we had a replica fall behind for a little while and > it caught up. It happens occasionally during periods of peak traffic, > and it looks like it caught up by the time of your second query.
Thanks, Toby. Note that when I loaded those bookmarks on the del.icio.us web page in Safari, it gave me the correct, updated data. Is it only the API which is susceptible to non-synced replicas? I mean, is it equally possible to, for example, delete a bookmark on my del.icio.us web page in Safari, reload the page, and have the deleted bookmark reappear? I've never seen that happen. Here is one possible kludge/workaround: If, as I have seen, http://del.icio.us/MyAccount is more likely to be true than the API, I could download the first page, parse it to find the total number of posts up at the top left, and warn the user if this does not equal the number of posts I get from the API posts/all. Besides being ugly as hell, this will only detect changes which affect the total number of posts. Are there any more effective workarounds? Also, is there any upper bound on the duration of replica-non-synced- ness? It was at least 30-45 minutes this morning. Jerry
