"Craig R. McClanahan" wrote:
>
> "Whaley, Dave (HQP)" wrote:
>
> > 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?
>
> Think of a session as a glorified Hashtable. ... There is nothing
> magic going on.
>
But there's magic as soon as the the web app is distributable,
no? I suppose it's fair enough that the design of a distributable
app needs to be different from a non-distributable app. You can't
(always) just set the "distributable" flag and expect things to
work. I've seen info (stealing heavily from advanced-servlets here :-)
along the lines of:
- 2-3k worth of session data to limit traffic
- Keep pointers to objects in distributed store, not the
objects themselves
- Just use your RDBMS
- Use vendor-specific solutions
- Just pin the user to a server
- Etc.
Is this all too container-specific, or are there some general
guidelines about what sorts of problems you can run into?
-cks
___________________________________________________________________________
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
