On 8/21/11 4:45 PM, "Justin Karneges" <[email protected]> wrote:
> 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. Seems to me that client writers are more likely to incorrectly think the server clock is going to be "right" than the other way around, but I don't care where the skew is added as long as it's specified which side does it, so we don't double-skew. -- Joe Hildebrand
