[Mono-list] A big (MS created) flaw in DateTime that surfaces in Web Services

[A Rafael D Teixeira]

>From: "Richard Norman" <Jazzynupe@sbcglobal.net>

>Now I may be wrong in this too, but isn't the offset used as a marker to
>indicate the time zone?

>So the time shown is 2 hours behind the GMT... so if you are going from say
>-2 to a -8 time zone, you would  take the destination time zone and 
>subtract
>the source and add those hours to the time ( take -8-(-2)= -8 + 2 = -6) 
>take
>away 6 hours from the time......

Yes, but the problem is: when calling a Web Service (or remoting), we want 
it to be a transparent medium ie it should not change the data it is 
carrying.

>So if I follow your example,
>
>  27/6/2003 14:00:00-6  sent to a time zone with +1 should become the
>following...
>
>(+1)-(-6) becomes +1+6=7
>
>So you add 7 hours to the time which then becomes 27/6/2003 21:00:00+1
>
>So if that is correct, and that is how it is handled internally, then we
>don't have a problem I believe

We still have 2 problems: MinValue and MaxValue drifting, and Daylight 
Savings non-simetric behavior.

Rafael Teixeira
Brazilian Polymath
Mono Hacker since 16 Jul 2001

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail