On 06/12/10 19:32, Fink, Andreas wrote: > It isn't a problem of sending the data in the wrong format, it's a > problem of Javascript (maybe only on some systems). > If I send the Java Date object back to the frontend, I get the correct > date back (of course, it is again wrong transferred from UTC to local > time). But my backend stores everything inside a database and other > applications (for example data exports to xls, csv or pdf) using the > data from the database. So this apps get wrong data. >
Well, my solution to that problem was to mandate users to choose a region upon first login. Whenever a date/time needs displayed, it's converted to the user's time zone in the server and sent with no time zones. When a date/time is sent to the server, the server does the conversion to UTC because the client always sends it with the region. Making conversions exclusively server side avoids such problems. burak ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
