DateValues rendered in GMT convey no timezone info, causing client side javascript mis-interpretation. #27

What steps will reproduce the problem?

1. Inserting a DateValue into a table requires that it be expressed in GMT
2. JSON renderer generates code to construct Date objects with 
year,month,day,hour,minute,second
3. Client-side javascript interprets date in local timezone

What is the expected output? What do you see instead?

I expect the client side to have enough information to generate correct local 
time values.


What version of the product are you using? On what operating system?

1.0.2, all platforms.


Please provide any additional information below.

You can solve this problem by having the JSON renderer generate millisecond 
past epoch constructors.  Then the client will construct dates properly since 
milliseconds past epoch are explicitly UTC, whereas date fields are interpreted 
locally.  As an added bonus, this will reduce the amount of data sent across 
the wire.