You can read this book: Web Development With JavaServer Pages.
- Original Message -
From: "Henry Hooi Tak Keong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 07, 2000 2:29 PM
Subject: Re: Servlet Controller - stopping other Servlets calling ac
CTED]>
Sent: Monday, August 07, 2000 8:34 PM
Subject: Re: Servlet Controller - stopping other Servlets calling action S
ervl ets
> Looks like a very good and easy solution. But won't that reduce
performance,
> in a way that say there are large number of request coming. Won't t
reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Hines, Bill
Sent: Monday, August 07, 2000 5:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Servlet Controller - stopping other Servlets calling action
S ervl ets
Easy - the controller servlet is the ONLY servlet in the application. It
calls "action classe
Easy - the controller servlet is the ONLY servlet in the application. It
calls "action classes" to carry out tasks, but there are not servlets. They
are "servlet aware" in that they accept servlet artifacts in their execute()
method as parameters, so they can access parameters, etc. But to answer
