I found this link with the simplest way to implement a login. To make this better you could
probably replace the direct call to JDBC with a proper dao.


--- Maya menon <maya_java@(protected)¿½:
> Hi,
> Looking for a best design strategy.
> Our client-server app is being converted to a web based app. The first feature to be converted
> is "Login process".
>
> I am planning to have a jsp page with user id[currently we dont request password from users],
> but I think password field is necessary. Now, when a valid user logs in, it should look at the
> database and display the messages available to the user from the database. This is what should
> happen.
>
> Now, there can be upto 1000 concurrent users. There can be 2500 users accessing the system in a
> 24 hour period.
>
> Which design pattern/patterns are best in a situation like this ?
> I am not a fan of EJB, but will EJB be helpful here ?
>
> Need all suggestions and links to similar problems and solutions.
>
> Thanks,
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)






___________________________________________________________
250MB gratis, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
http://correo.yahoo.com.ar

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)