on 11/29/99 12:29 PM, David Hildebrandt <[EMAIL PROTECTED]> wrote:
> 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)
I have started a project to help with this issue...
<http://java.apache.org/turbine/>
-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
