Nathan Bubna wrote: > Gabe said: ...
>>My expectation was that simple tools like a date formatter should be >>thread-safe such that we can reuse instances. If the tool is not >>thread-safe, the only reasonable and safe scope is 'request' in my view. >>If something like a date formatter can't even be reused, what can? >> > first of all, session scope is just as safe as request. the only scope > where thread-safety is a reasonable concern at all is application. Thread-safety is an issue for session scoped tools as well. The requirements are somewhat different thought. Think about a web client loading a frame-set page. It can easily generate multiple virtually concurrent requests that are all within the same session. ... > arghh!! how can you not see the case for that!!!?!!!??! i have spelled it > out for you time and again!!! please read this ****i want a DateTool that > can be easily used (or at least easily extended) to work reasonably in > either application, session, or request scope!!!**** what is so hard for > you to understand about that? if you'd like other cases, how about pretty > much any tool that relies heavily on localization?! sorry if i seem a > little exasperated about this, but if i'm do then it's probably because i > am! this is not a non-issue or unrealistic case! this is a very simple, > specific, and real case that i must have repeated to you about ten times by > now!! and i'm not feeling very patient today! sorry. We are talking past each other here. I hear what you are saying but you are not addressing my input. That's why repeating the same thing doesn't resolve the issue. Let me come back to this topic in a few days. I noted that there are some open points here. Gabe -- Gabriel Sidler Software Engineer, Eivycom GmbH, Zurich, Switzerland -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
