Re: Thread Safety: Was (Native sFTP?)

I agree completely. Threads, in sense, are dangerous. They sound great and
make performance better (sometimes), but it's hard to be truly thread safe
100% of the time. I'm not saying you shouldn't be, it's just hard.

When I first started with Java I thought threads were going to be the best
thing ever. I quickly found out there's a lot more to it than Thread t = new
Thread(). I have basically found very few reasons to use a thread, except
for UI's.

Thanks for the comments, it actually made me look at the example and realize
what I should have done. I appreciate it.

--
James R. Perkins


On Tue, Apr 28, 2009 at 07:50, Walden H. Leverich
<WaldenL@xxxxxxxxxxxxxxx>wrote:

but it was just an example.

Yup. And my example would have been the same. My point is simply that
thread safety is in no way as simple as people think it is. Things can
be obviously not thread safe, but things that can appear to be thread
safe may not be either.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.