Re[2]: servlets

[Jacob Kjome <ho...@visi.com>]

Hello Felipe,

Note that the invoker servlet provided in Tomcat as the mapped path
/servlet/* will create a separate instance of your servlet to one that
you access via a normal servlet mapping such as /myservlet.

So, you *can* get two instances of a particular servlet at one time.
Disabling the invoker servlet (as is the default currently) resolves
this issue, however.

Jake

Tuesday, January 28, 2003, 4:43:36 PM, you wrote:

FS>   Yes, that's cool :-)))
FS>   Anyway, if you have multiple tomcats one would not see others
FS> instances, so no prob at all.
FS>   I don't think anyone would use SingleThreadModel... it's practically
FS> useless

FS> On Tue, 2003-01-28 at 20:32, Wendy Smoak wrote:
>> Craig wrote
>> > The servlet spec guarantees that you will get a single instance of a
>> > non-SingleThreadModel servlet PER <servlet> DEFINITION for that webapp.
>> > See Section SRV.2.2 of the Servlet 2.3 spec for the formal details.
>> 
>> Interesting... I was under the impression that the container was free to
>> create as many instances of your Servlet as it wanted to, but that appears
>> to be the case *only* for SingleThreadModel.  (Does anyone actually _use_
>> that?)
>> 
>> So as long as you're not in a distributed environment [multiple Tomcats?]
>> and not implementing SingleThreadModel, it appears you *can* assume that
>> there will be only one instance of your Servlet.
>> 
>> -- 
>> Wendy Smoak
>> Applications Systems Analyst, Sr.
>> Arizona State University PA Information Resources Management
>> 



-- 
Best regards,
 Jacob                            mailto:hoju@visi.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org