At 01:47 PM 5/13/99 , K Shaikh wrote:
>
> We're developing a large project using Servlets.
> We are trying to decide between using a single
> big servlet responding to all HTTP requests or a
> bunch of smaller ones to server different
> types of requests. Does anyone
> have any ideas why one may be better than the other?
>
I am on a team of two developing a small project using a single servlet
implementing the SingleThreadModel. It interfaces with multiple forms, and
depending on the form and the forms request parameters, the Service method
dispatches the request/response objects to various objects that know how to
handle the request and formulate a response (usually from an SQL query). The
response is formulated using an HTML parser (the Tags package from
HotHouseObjects.com) to insert the relevant data into HTML template pages.
For our project this helps us to not have to worry about pooling
connections/etc.
This is my first project with servlets, but I am doing it this way on the
advice of several other servlet gurus here at work.
FWIW,
LCB
___________________________________________________________________________
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
