"Craig R. McClanahan" wrote:
>
> You can use these kinds of sites for examples of how to deal with the user
> interface issues involved. In a servlet environment, sessions make it pretty
> easy to implement these kinds of things.
Using Apache as web server, there is a reason to have your own session
handling, as opposed to servlet engine session handling. If you manage
your own sessions, you can combine this with mod_rewrite to let Apache
serve requests to protected areas only if a session has been
established.
An extreme thought, and my reason to use this approach: if requests to
all protected areas are going to be served by a file servlet instead of
Apache, why use Apache (or any web server) ?
Carlos
___________________________________________________________________________
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
