sure, you could do it given enough hardware resources, but it would be *murder* on performance. just about all servlet engines offer some form of failover for HTTP Sessions, usually by persisting the data somewhere, or (in the case of weblogic) through multicast in the cluster. the overhead of persisting that amount of data would most likely slow your application to a crawl.
you could use stateful session beans, but again, i don't know how good a choice that might be given the volume of data. if you can provide some details of the exact situation, i.e., what this data you're persisting is, maybe i could provide some more focussed advice. ashwin -----Original Message----- From: S Itzkowitz [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 9:50 PM To: [EMAIL PROTECTED] Subject: HTTP Session Caching Large Amount of Data Should there be a problem with caching 3MB of data in an HTTP Session? The server has 256 MB memory reserved for the application to cache. The HTTP Sessions will be invalidated every 30 minutes. The application server being used is IBM websphere. Thanks for any help Susie [EMAIL PROTECTED] ___________________________________________________________________________ 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 ___________________________________________________________________________ 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
