-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 3/10/15 8:15 PM, David Bullock wrote:
> On 11 March 2015 at 04:43, Christopher Schultz
> > wrote:
>
> Basically, making a
>> servlet threadsafe only requires you to avoid any non-threadsafe
>> class members in the servlet itself...
>
> S
On 11 March 2015 at 04:43, Christopher Schultz wrote:
Basically, making a
> servlet threadsafe only requires you to avoid any non-threadsafe class
> members in the servlet itself...
>
Since we're tossing pennies, I've often wondered how the app-server
achieves the effect that any instance-level
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carl,
Others have already responded, but I figured I'd add my two cents, too.
On 3/10/15 11:25 AM, Carl Dreher wrote:
>> If I write a servlet such as the above, is there ever only once
>> instance of it running?
>
>>> Don't confuse objects with t
Unsubscribe.
Please?!
-- Kaydell
kayd...@yahoo.com
On Mar 10, 2015, at 9:25 AM, Carl Dreher wrote:
>> If I write a servlet such as the above, is there ever only once instance of
>> it running?
>
>>> Don't confuse objects with threads. There is one instance of a particular
>>> servlet, bu
Hey Carl,
On Tue, Mar 10, 2015 at 11:25 AM, Carl Dreher wrote:
> If I write a servlet such as the above, is there ever only once instance
>> of it running?
>>
>
> Don't confuse objects with threads. There is one instance of a
>>> particular servlet, but many threads may be executing in it conc
> From: Carl Dreher [mailto:focus...@arn.net]
> Subject: Re: threads vs. servlets
> > > If I write a servlet such as the above, is there ever only once instance
> > > of it running?
> > Don't confuse objects with threads. There is one instance of a par
If I write a servlet such as the above, is there ever only once instance of it
running?
Don't confuse objects with threads. There is one instance of a particular
servlet, but many threads may be executing in it concurrently, with each thread
processing a separate request.
I understand tha
