I think it should work, but I'm not absolutly sure. Since you can't
select the time zone in the calendar (hopefully!), you may be right to
avoid transfering timezone information, because it could change the day
when going from/to the server to/from the client.
Example.
I'm at GMT+11. If write the following javascript:
var d = new Date("Mon Oct 20 00:00:00 GMT+1200 2008");
document.write("<p>"+d+"</p>");
It gives me:
Sun Oct 19 2008 23:00:00 GMT+1100 (NCT)
While for this javascript:
var d = new Date("Mon Oct 20 00:00:00 2008");
document.write("<p>"+d+"</p>");
I get:
Mon Oct 20 2008 00:00:00 GMT+1100 (NCT)
Given the semantics of the calendar (I write "10/20/2008", I want to see
"10/20/2008" on the server side), I think its better to avoid timezone
information.
Le vendredi 17 octobre 2008 à 06:27 -0700, Howard Lewis Ship a écrit :
> The fix I implemented was to use a simple number (milliseconds since
> the epoch) as the transfer format. I'm concerned there may be a time
> zone issue though, when the browser time zone is not the same as the
> server time zone.
--
.~.
/V\ Mikaël Cluseau <[EMAIL PROTECTED]>
// \\
/( )\ ISI.NC +687 26.93.18
^`~'^
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
