On Dec 21, 2004, at 11:41 AM, Mark R Durman/CA/US/MQSolutions wrote:
Setting the Time Zone to UTC does enable correlation of events across servers in different time zones (assuming they are all synchronized with a common time source). WebSphere MQ stores all timestamps in UTC for that reason. For a distributed application, this can be useful.
If the user can set the TZ at the appender level, why not support a TZ at the repository level as well? Most of the time it won't be used, but if a user wants all appenders to use a non-default TZ they can set it there.
Allowing TZ to be specified at the repository level would add an interaction between layout and repository that I don't believe currently exists and I don't see it adds much additional value. I think that we should pick one place to add it and the gather feedback to see if we picked the wrong place or need to add additional specification points.
Do you have a preference between specifying timezone within the pattern layout (which would allow multiple time renderings in difference zones within one rendered message) or as an attribute of the layout.
The distributed app scenario also supports the outputting of events through different appenders in different languages. I worked on a large airline reservations system in Germany a while back that had support groups in Germany, France and Italy. I'm sure they would have liked to see events in their own language. It also comes into play for product support--a support group may want a customer to enable an appender for troubleshooting and have the events output in the language they understand, not the language the customer uses.
I don't see the use case as unreasonable and think that it should not be prematurely discarded. It will take a bit of exploring to see how hard and expensive (or not) it would be in practice.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
