binary protocol time representation

[Dan Farina]

On Thu, 2007-07-12 at 14:16 +0200, a. wrote:
> Ticks are easy in .NEt, but I'm much more concerned about the  
> "meaning" of that specific time.
> 
> If my server runs DST but one of the clients is on CET, and the  
> client sends 2007-07-12 12:00 AM, what does it mean? 12:00 in DST or  
> CET?
> 
> We either should declare that absolute expiration should treated as  
> UTC, or get rid of it and use relative expirations.
> 

Yes, either of these makes me more happy than the current situation.

I generally don't like absolute times unless absolutely required,
though. Relative time is robust to all sorts of things for free like
massively mismatched clocks and, as mentioned, time zones.

df