> I have developed a few projects with servlets and can give you the following
> advice. One big servlet defeats the current movement toward componentizing
> applications. One big servlet is very tough to debug, update, and is not
> practical to use in other projects because it is doing to many things when all
> you want is one or two of the methods. As an example I designed a reporting
> project with servlets. I too had to decide between one servlet or many.
If you all want a framework to help you with Luther's advice, check out
Dash.
<http://www.working-dogs.com/dash/>
The CVS version is more stable than the 1.0a1 release so I suggest that you
grab that.
-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
