Hello, I saw that features, but still not sure how this timezone will work - relatively to what time? Client or server side? Or will it depend on in which tier (server or client) you work? Or it will just add or subtract some time from date and time variable? - which still will do no change to server now() displaying on client problem.
Still I will be stubborn :) with our opinion, that more natural way is that time should always stay as it is on each side (created on client side - client time, created on server side - server time). Then date and time should behave like any other variable - never change if no one asked it to change, when passing its data through client and server side, except you implicitely ask it to change it with some additional modelling using relative date and time or other models with timezone trigger (where you know exactly how many hours, minutes) you want to move specific time. We think, it's better to send just additional info about client timezone [so we can model, if we want, relative time to server (we know what timezone client is and server is)]
Maybe some other forum users could have a word about this? We don't know if someone is doing multitimezone applications here or have different opinions? Maybe we're misreading everything...
Hope for more discussion :)
Ultimately, good solution may be extra input not mandatory trigger <adjusttime> (default Yes) to all time related models. If we don't want time to change between tiers we would set this trigger to No. Other solution would be global parameter for whole application. I don't know implementation specifics so I'm just guessing what would be more simple.
For best results, use the Firefox browser..