Question for those familiar with Java ....

[temp2]

Hello,

I've done some Java in the past. I don't remember ever having to worry
about updating a control from a thread other than the one that created
it. In C# you have to jump throught a bunch of hoops to with Invoke/
BeginInvoke or use tricks with BackgroundWorker. I don't remember
having to do this with Java. Java runs is in a "managed" environment
like C#. Is it because Swing is thread safe?

TIA

[Jon Skeet [C# MVP]]

<te***@cfl.rr.comwrote:

I've done some Java in the past. I don't remember ever having to worry
about updating a control from a thread other than the one that created
it. In C# you have to jump throught a bunch of hoops to with Invoke/
BeginInvoke or use tricks with BackgroundWorker. I don't remember
having to do this with Java. Java runs is in a "managed" environment
like C#. Is it because Swing is thread safe?

No, Swing has the same rules as Windows Forms. That's what the
SwingWorker class exists for. See
http://java.sun.com/docs/books/tutor...ncy/index.html

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[PS]

<te***@cfl.rr.comwrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...

Hello,

I've done some Java in the past. I don't remember ever having to worry
about updating a control from a thread other than the one that created
it. In C# you have to jump throught a bunch of hoops to with Invoke/
BeginInvoke or use tricks with BackgroundWorker. I don't remember
having to do this with Java. Java runs is in a "managed" environment
like C#. Is it because Swing is thread safe?

A quick google shows that Swing is primarily not thread safe. You were
probably just lucky in the past that nothing went wrong.

http://groups.google.com/group/comp....3b1cd60d7e422b

PS

TIA

[Mugunth]

On Mar 8, 3:05 am, "PS" <[e-mail]:

<[e-mail] in message

news:11**********************@p10g2000cwp.googlegr oups.com...

Hello,

I've done some Java in the past. I don't remember ever having to worry
about updating a control from a thread other than the one that created
it. In C# you have to jump throught a bunch of hoops to with Invoke/
BeginInvoke or use tricks with BackgroundWorker. I don't remember
having to do this with Java. Java runs is in a "managed" environment
like C#. Is it because Swing is thread safe?

A quick google shows that Swing is primarily not thread safe. You were
probably just lucky in the past that nothing went wrong.

http://groups.google.com/group/comp....e_thread/threa...

PS

TIA

A reason why UI Components are not thread safe are because, any update
to UI components should not be blocked by a running thread as a block
on UI update would bring about a slow, non-responsive UI. This
violates the design goal of a Graphical User Interface.

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

PS wrote:

A quick google shows that Swing is primarily not thread safe. You were
probably just lucky in the past that nothing went wrong.

Similar to .NET 1.1, which does not check like 2.0 does.

Arne