> There is also another possiblity. You can use the class as a shared object so
> that it is cached but it is not a servlet. This keeps you from having the
> overhead of a Servlet but you have the benefits of persistantcy for speed. I
> use shared objects often when I want servlets to communicate with each other
or
> when I have code that I want to use often but is better off in a component so
> that I can reuse it and it has no need to inherit the Servlet properties.
With
> a shared object you get the best of both worlds. A persistent object that can
> be accessed through the getInstance() method and it does not have the overhead
> of a Servlet.
>
> Luther
This is exactly what my Dash framework does...
<http://www.working-dogs.com/dash/>
-jon
___________________________________________________________________________
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
