I am building an application that needs to track ten objects, up to 42K
each, for each user. The most convenient way to do this is to store the
objects in the session until we are ready to write them to the database.
The app server is Weblogic 5.1. Are there any technical limitations we will
run into?
The transaction volume is light, as well as the concurrent user load. The
user will be paging through differnet servlets in order to complete the
building of the object. The alternative way of handling the object build is
to use the database as a "workfile". The problem with that is finding and
deleting abandoned work records if the user hits the cancel button.
Documentation on the session object seems hard to come by. I've checked
Sun's Developer Connection as well as the Weblogic site. Even books on
Servlet programming don't talk about it much. Where do you find out the
nitty gritty?
. . . . . . . . . . . . . . . .
Dave Whaley
Developer, Web Applications
Robert Half International, Inc.
(925) 598-5256
. . . . . . . . . . . . . . . .
___________________________________________________________________________
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
