Re: Object (servant) lifecycle

Scott Ferguson wrote:
>> How many servant objects will there be ?
> One. (I had to check, though.)
>
> I think it's pretty much a consensus that automatic servant pooling is a
> bad idea because it doesn't really avoid the need for threading and just
> makes things more complicated.
>
> -- Scott
>

Thank you very much for your swift reply!

So, as I thought, Resin creates 1 servlet that in turn creates 1
implementation, and it's methods are called in a multi-threaded fashion
basically from the IO threads.

That means that I would have to "thread-safe" any objects created by the
servant, such as the JMS producer if I make it an instance variable
instead of re-creating it on each call.
Is the above correct ?

Un-related question: latest Resin docs list an JMS implementation. What
is it, any docs/specs on it ?

Kind regards,

-- 
Radu-Adrian Popescu
CSA, DBA, Developer
Aldrapay MD
Aldratech Ltd.
+40213212243