I can't think of any use cases for user timezone. - Dave
On 12/5/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
Is there any reason to continue maintaining a user timezone? we never use that to calculate anything so it seems like it's just a point of confusion. -- Allen Jeffrey Blattman wrote: > admin API accepts and returns dates as a unix timestamp (ms since > 1970-01-01, long). it accepts and returns timezones (user and weblog) as > a timezone id (TimeZone.getID()). > > Dave wrote: >> I don't think we have timezone handling documented anywhere. >> Here's how I think things work: >> >> - Each weblog has a timezone >> >> - Each user has a timezone >> (Used only as default when user creates a new weblog) >> >> - Dates are stored in a timezone free universal format (UTC?) >> >> - When displayed on a weblog, entry dates are converted to weblog's >> timezone >> >> - In weblog entry form, date are displayed and processed in weblog's >> timezone >> >> - Incoming MetaWeblog API posts include date with timezone and Java >> date parsing converts them to universal format for storage. >> >> >> - Dave >> >> >> >> On 12/3/06, Anil Gangolli <[EMAIL PROTECTED]> wrote: >>> >>> Do we have a clear description of our treatment of timezone anywhere? >>> >>> I think we have several minor timezone-related bugs, but before >>> looking at them, I'd like to make sure we first have a consistent >>> proposal for how timezone should be treated. >>> >>> --a. >>> >>> >>> >>> >>> >>>
