Maybe I'm overlooking something obvious, but CF's internal date handling seems a bit odd to me. Anyone else noticed anything along these lines?
Basically, while playing around with manually constructed WDDX packets, I noticed that the UTC offset returned by GetTimeZoneInfo() reflects the Daylight Savings status of the server, but the WDDX serialization process doesn't. I went into this in more detail in my blog: http://journurl.com/mxblogspace/users/admin/?mode=article&entry=388 Don't get me wrong... it works once you understand it. But man, I spent some serious head-scratching time while trying to sort out what CFMX was doing. And since the same thing seems to happen in CF5, I can't even blame it on MX. -- Roger Benningfield http://admin.support.journurl.com/ JournURL: MXBlogspace free blog hosting for CF/Flash developers http://journurl.com/mxblogspace/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
