On Saturday, August 20, 2011 12:11:05 AM Joe Hildebrand wrote: > On 8/19/11 12:12 PM, "Justin Karneges" > > <[email protected]> wrote: > > Indeed. In my case I consider a time-based query to be inclusive, so as > > to not miss updates occuring within the same second. In the rare case > > you pick up the same item again, it's harmless. > > I'd go a little further, and suggest that the publishing server should back > up enough time to account for clock skew, and republish everything from > that earlier time. 5-10m should do it, as long as there aren't a lot of > items.
Good catch, I didn't consider clock skew. I wonder if the client should just specify a timestamp 5-10m in the past instead of having magic at the node servers. Then accurate time queries (made relative to timestamps of other items provided by the server) stay optimized. Justin
