[EMAIL PROTECTED] wrote: > <snip> >> >> But anyhow, Servlet instances are _recycled_. Once a servlet >> instance is done processing a request, it will be reused for a >> future request. <snip> - Geoff > > Isn't this only true if you've set CacheServletInstances to a non zero > value? It may be a quibbling point, but if you set this value to 0, > it shouldn't be recycling servlet instances anymore, right? > > Its possible I misunderstand the meaning behind that configuration > value, but thats the meaning I've been assuming. Depending upon how > heavy your traffic is or how large your servlet classes are some > people might not be switching that value to non zero in a production > version of their application. > > Admittedly, this doesn't in any way detract the from the rest of what > you said. I just wanted to get clarification on servlet recycling and > caching.
You are correct. CacheServletInstances does default to True in the config file, so in the absence of any changes to the configuration, servlets will be recycled. I believe you can also override this behavior on a servlet by servlet basis by providing a "canBeReused" method or something along those lines. So if you need one particular servlet to be constructed anew on every request, there's a way to do that. - Geoff ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
