On Wed, Jan 13, 2010 at 7:23 PM, Cody Caughlan <[email protected]> wrote:
> Hmm, I think thats normal behavior. It sounds like you're suggesting
> that the JSON serializer should encode a Date as
>
> "{ts '2010-01-13 19:09:09'}"
Not quite. I probably wasn't clear. The formats I was giving were
the formats BEFORE the serialization.
When CF serializes the two formats, here are the results
{ts '2010-01-13 19:09:09'} --> January, 13 2010 19:20:48 [a valid JS
date format]
2010-01-13 19:09:09 --> 2010-01-13 19:09:09 (not a valid JS date format)
Now, if I manually run an inline query for that same object and
serialize the query, the date gets formatted correctly.
>
> Microsoft has a blog post on this here:
>
> http://weblogs.asp.net/bleroy/archive/2008/01/18/dates-and-json.aspx
>
> They say: "The second approach, which is what most people settled on,
> is to adopt some string form of date and just interpret any string
> that conforms to this format as a date."
>
> Which is what we have done as well.
>
Their final solution seemed to be exploiting a loophole in JSON
itself, which would worry me, since loopholes can be closed. :)
Besides, if I have to manually format the object, then I lose the
benefit of using serializeJson() and I can just go the query / manual
formatting route.
Scott
--
-----------------------------------------
Scott Brady
http://www.scottbrady.net/
--
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
