On Tue, 18 May 2004, Zerbe John W wrote:
| With the introduction of EJB 2.0 Message Driven Beans, you no longer
| need to start and manage your own threads to do asynchronous processing.
J2EE sucks.
I use tons of Threads in my Serlvet environ.. Well, 20-30 workers..
If you know what you're doin
dre
| Stølsvik
| Sent: Tuesday, May 18, 2004 10:25 AM
| To: [EMAIL PROTECTED]
| Subject: Re: Thread Question
|
|
| On Tue, 18 May 2004, Zerbe John W wrote:
|
| | Why do you think you need to start threads in a J2EE application?
|
| This is "-SERVLET- interest".. So I presume he's tal
g are now the container's responsibility.
-Original Message-
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED] Behalf Of Endre
Stølsvik
Sent: Tuesday, May 18, 2004 10:25 AM
To: [EMAIL PROTECTED]
Subject: Re: Thread
PROTECTED]
Subject: Re: Thread Question
When we can embed multi-threaded code in a Servlet, then how is it going to
compete with the Threads spawned by the Container? Won't they both clash for
the CPU?
regards,
-jayprakash
-Original Message-
From: A mailing list for discussion about Su
ervlet
API Technology. [mailto:[EMAIL PROTECTED] Behalf Of Endre
Stølsvik
Sent: Tuesday, May 18, 2004 7:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Thread Question
On Tue, 18 May 2004, Zerbe John W wrote:
| Why do you think you need to start threads in a J2EE application?
This is "-SERVLET- interest&
On Tue, 18 May 2004, Zerbe John W wrote:
| Why do you think you need to start threads in a J2EE application?
This is "-SERVLET- interest".. So I presume he's talking about servlets.
Yes, he is.
The answer to the original question is most probably "yes".
Endre
|
| -Original Message-
| F
Why do you think you need to start threads in a J2EE application?
-Original Message-
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED] Behalf Of
Karthikeyan
Sent: Tuesday, May 18, 2004 4:46 AM
To: [EMAIL PROTECTED]
Subject: T
