>but the CFC is still broken as there is still an issue w/ dateConvert(). >did the >new one i sent work "better"?
Sorry Paul, I didn't receive a new one from you. I tested using the older version I had and the latest version from your site. Both produced the same results. >From what I understood of your blog post the issue with dateConvert() is that you can be x hours out during a DST switch over period. Using UTC or epoch as oppose to server time would resolve this. The thing I can't get my head around (and what made me think this was a JVM issue) is the fact that on Sunday: getRawOffset was reported correctly, -5 inDST was reported correctly, yes getDST was reported correctly, +1 getTZOffset was NOT reported correctly, -5 But today, offset is reported correctly as -4. Looking at the code, it doesn't look like dateConvert() factors in the above methods. This stuff is confuuuusing :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:272344 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
