On Dec 22, 2008, at 11:32 AM, Florijan Stamenkovic wrote:
Hi all,
I am recording daily currency conversion rates.
The problem I have is that at the moment currency information can be
input from wherever on the planet. Now, most users will deal with
date info only, when it comes to currency info, leaving time and
timezone issues in Java's hands. Java seems to automatically set a
parsed date to the time of 00:00:00 in the current timezone. What I
am thinking of is "normalizing" dates after input. Essentially
extracting the date (textually) from the Date that Java parsed, and
setting it to 12:00:00 GMT, in hope that will ease qualification /
filtering later on.
So, does anyone do this? Does anyone have a better strategy? This is
the first time I am doing stuff with dates requires tight control of
what's happening...
I do this, but I usually only work over 2-3 timezones. World wide,
this might still have some issues. I hate thinking about dates and
times. Bring on the goats!
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
