Madhavi:
I must second Jon's comment - this design is working very well for me as
well, having basically a single servlet that calls other objects to do the
actual work. I've found that this keeps your business objects "decoupled" so
they can be used from JSP pages as easily as from servlets.
My 2c worth!
Mike
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's
> Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
> Madhavi Karanam
> Sent: Friday, December 03, 1999 4:21 PM
> To: [EMAIL PROTECTED]
> Subject: Which is a Better Design?
>
>
> I am designing servlets and thinking of routing all the
> requests from the
> users through one servlet to check for the authorized users.
> I am not sure whether this is a good design or not.
> If we check for user authorization in different servlets then
> we need to put
> the code in all the servlets or some servlets.
>
> Can someone advise me which is a good design can something
> different from
> the above mentioned two. Performance is also an issue here.
> Thanks in advance
> Madhavi
>
> ______________________________________________________________
> _____________
> 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
>
___________________________________________________________________________
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
