Hello Everyone:
Preamble
The client-server architecture of Java servlets imposes a strict
request-response relationship between browser and server. This helps limit
the number of application states and rationalizes application functionality.
HTML pages further underline the possibility that user experiences and
servlet functionality may be nicely divided into coherent portions, even
separate servlets. For instance, typically a user 'logs in' and the servlet
responds with either a 'proceed' or 'rejection' page. The presentation,
logic and occurrence of this operation within a session changes little from
application to application. One servlet (i.e. Login Servlet) could satisfy
most 'login' needs across a single organization. (I use the word
'application' in its broad sense to encompass 'servlets' and to mean 'to
apply', as opposed to standalone executables)
Questions
Do seasoned Java servlet developers find themselves dividing frequently
recurring application functionality used in a set of servlets into separate
servlets? That is, do they move from 'monoliths' to 'co-operating servlets'
in their application design?
Is the development of a class library preferred over development of a
servlet library? (Right now, I am inclined to encapsulate most
functionality using classes. I would still be inclined to subordinate any
'co-operating servlet (please pick a better name)' to that of a wrapper
around a good set of classes unless I hear good reasons for another
treatment.)
What are the positive and negative ramifications of this tack in terms of
application performance, limiting factors to the application, project
organization, testing, or cost?
Any help or referrals would be of interest. I found little directly
applicable in the archives and I know similar concerns have recently been
raised here.
Thank you and regards,
David Hildebrandt
___________________________________________________________________________
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
