<<You can implement anything you want>> I figured that. But SingleThreadModel is a 'marker" interface which really acts as a suggestion to the servlet engine, it's only useful because the servlet spec tells web containers to NOT hit that servlet concurently.
<<why would you want to?>> My filter (or one of it's instance variables) is not thread safe. I figured if the web container pooled the filter that would suit my needs just fine. Dave Ford Smart Soft - The Developer Training Company http://www.smart-soft.com ----- Original Message ----- From: "Mark Galbreath" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 14, 2001 2:55 PM Subject: Re: SingleThreadModel Filter > You can implement anything you want; why would you want to? > > Mark > > This email scanned with Norton AntiVirus 2002 > > > ----- Original Message ----- > From: "Dave Ford" <[EMAIL PROTECTED]> > Sent: Friday, December 14, 2001 5:45 PM > > > > Can a Filter implement SingleThreadModel? > > ___________________________________________________________________________ > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff SERVLET-INTEREST". > > Archives: http://archives.java.sun.com/archives/servlet-interest.html > Resources: http://java.sun.com/products/servlet/external-resources.html > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html > ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
