Hmm I've got another problem with date and time models...
There is one app server and two browsers for this test.
Browser nr 1 gets to app through localhost (it's on the same computer) so is in the same timezone
Browser nr 2 time is relatively to 1st browser -9 hours.
On client side, I'm using Relative Date with:
<Days> trigger = 1
<Base Date> = '2009-08-28'
Browser nr 1 exit = 2009-08-29 (correct)
Browser nr 2 exit = 2009-08-28 (not correct)
<Days> trigger = -1
Browser nr 1 exit = 2009-08-27 (correct)
Browser nr 2 exit = 2009-08-26 (not correct)
This is all client side, so it's strange I get two different results. When I insert this relative date model to service it works ok, but generates extra POST to server which is unefficient.
This problem is becoming severe for us, cause we want our application to have international range.
Could you (as usual) give us a hint when approximately this problem will be solved? We'd like to know If we need to start rebuilding our system and put all date models to services, or if they can stay a bit longer and we'll wait for solution?
For best results, use the Firefox browser..