tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Sandberg...@cs.stanford.edu>
Subject Re: SSI Servlet has big problems
Date Thu, 02 May 2002 04:39:23 GMT
Remy Maucherat wrote:

>>Implementing the SingleThreadedServlet interface will not help thi
>>
>
>Are you sure ?
>(I didn't look at the code at all, so I'm just wondering)
>Otherwise, it would be a really cheap way to make it work.
>
>Thanks for looking into it anyway.
>  
>

Implementing SingleThreadedServlet doesn't mean only one thread will be 
running the servlet at a time.  It means only one thread will be running 
a given INSTANCE of the servlet.  So you could still have two threads 
running two different instances of the same servlet.  This will still 
get massively messed up with all the sharing of static variables.

>>Are the two authors still mantaining this code?  Bip Thelin? Amy Roh?
>>    
>>
>
>Not really. I didn't hear about Bip for a while, and Amy has been busy with
>other things.
>Usually an easy way to get commit access if you have time to dedicate to
>contributing is to take over the maintenance of some abandoned component(s).
>CGI also needs a maintainer, BTW.
>
>Remy
>
I'll fix this problem, and I'll create a filter that does SSI on any 
output ( so that a JSP page can use SSI, for example ).  I don't have 
any interest in being a maintainer/having commit access, however.

So what's the best way to give back my bug fixes/filter?

Thanks for the response, btw.

-Dan



--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message