then your design needs to be looked at. Usually I try to maintain a strict servlet : activity(for want of a better word) as close as a 1:1 relationship. oo design ie you would not have func for customer creation within and accoutn object. So I would have a login servlet deal with login functionality. In any case this does not stop you from having a login jsp that does the job that you have explained. You also ensure that any maintenance only needs a java developer instead of a java developer with cgi knowledge etc
On Friday, Nov 8, 2002, at 18:44 Etc/GMT, Aryeh Katz wrote:

why are you not using JSP then.  this is what its designed for
The servlet doesn't just handle login. Login is just called most often, and is
most expensive.

---
Aryeh Katz
VASCO
www.vasco.com


--
To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Reply via email to