>This is more a design and performance issue then a good or bad issue. Servlets >are started and remain running and can serve multiple users with out having a >new instance started. Servlets allow some amount of persistance while dealing >with requests. As JSP gets used more.... the business logic of the servlet can >be seperated from the presentation layer of the JSP and it becomes a better >(there's that word again) development environment. Of course there is no need >to download any java/class files when running a servlet, since it receives HTML >requests and serves HTML, removing the firewall issues. >Royce Thank you. This is what I was looking for. +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.