Hi Madhavi,
Just curious :
How do you check for user authorization ?
I'm wondering why it's necessary to use a *servlet* to do the auth. chk. ?
Can't a plain Java method of an AuthChk class, say, be used instead,
by passing it the necessary parameters ? It could return a boolean
indicating whether the user is authorized or not. Or is it some
servlet-specific kind of checking you need to do which is
better handled by a servlet ?
No doubt, though, that having the check centralized is the way
to go - as long as the same kind of check is required in all the
servlets.
In either case (whether using a AuthChk servlet or an AuthChk (non-servlet)
class)
you would get the advantage of having code to maintain/debug in only one
place.
Vasudev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Vasudev Ram
Infosys Technologies Limited
Pune, India
Email : [EMAIL PROTECTED]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
On a clear day you can see the blue screen of death.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> -----Original Message-----
> From: jon * [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, December 04, 1999 6:08 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Which is a Better Design?
>
> on 12/3/99 1:21 PM, Madhavi Karanam <[EMAIL PROTECTED]> wrote:
>
> > 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
>
> That is a GREAT design. If you take a look at Turbine, this is how I
> designed it as well...
>
> <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
___________________________________________________________________________
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
