|
There is not much to handle here. I would consider something like Struts or Spring, which helps address Dieter's earlier concern about separation of code. You business logic should know nothing about servlets, jsp, or presentation. In most cases, you will not need anything fancy to manage threads or sessions. Any servlet engine should pool threads and provide a thread for each request. You may need to tune this some but in reality it doesn't change overall performance very much. Sessions in servlets are limited somewhat because most Web browsers will share sessions when a user requests a new window. This is seldom a problem and you can almost always just build an adapter that stores your business logic related objects in a session-scoped container. David Morris >>> iva030@xxxxxxxxx 3/8/2004 11:10:48 AM >>> ...Then that leaves state mgmt, threading and transaction control to be dealt with... Thx!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
