I'm pretty new to this .jsp/servlet arena, and now that I have to start conversion of an old perl/cgi app I'm not quite sure how to structure it. Here's my situation/question:
I've got one db to connect to, need authentication / sessions, and need to use .jsp's for layout. Concurrent access is not very likely, but I like to be thorough and guard against it anyway. Is it better to use a javabean to maintain a common db connection / session or to have a servlet handle all requests and forward results to jsp? I haven't done either, so I don't know their strengths or weaknesses. Any help would be appreciated. If it matters, the platform is Redhat 7.1 using Apache 1.3.22, Tomcat 4.0.4, mod_jk, and MySQL. The old app is a collection of separate perl cgi scripts that maintain sessions by a url attribute. Noel Peden Library Systems Administrator Pierce Library - EOU 541.962.3017 [EMAIL PROTECTED] http://pierce.eou.edu You cannot make a man by standing a sheep on its hind legs. But by standing a flock of sheep in that position you can make a crowd of men. - Max Beerbohm ___________________________________________________________________________ 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
