umm... pretty much all of it.
If you're allocating all the objects you deal with inside your
components, you probably aren't faced with many issues, but any time
you start considering anything that is shared, you have to consider
the fact that java is natively multi-threaded, and there are always
other threads running, even if you're not concurrently handling
requests.
For instance, if you always instantiate a formatter inside your
component and that thread is the only one that know about it, you
should be fine. However, if you're sharing an instance (usually for
performance reasons), you need to be aware of the fact that it could
be called from multiple places at the same time.
Ken
On Jul 9, 2008, at 10:18 AM, Gennady Kushnir wrote:
Hmm...
I'm not quite shure in what parts of WO programming it is vital to be
thread safe?
2008/7/9 Ken Anderson <[EMAIL PROTECTED]>:
I'm sure Pierre could answer this better than anyone else, but I
always lock
NSTimestampFormatter when used in multi-threaded situations...
On Jul 8, 2008, at 7:03 PM, Chuck Hill wrote:
Also note that unlike NSTimestampFormatter, SimpleDateFormat is
not thread
safe. At least NSTimestampFormatter is not documented to be non-
thread
safe.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
