John,
> Are there any downsides to putting objects in the HttpSession Object (as
> opposed to strictly using request/response).
All session-bound objects have to serialisable (which can cause
problems), due to the session constantly saved and restored.
Therefore if you have large data objects, it would be better to store
references to the these objects rather than the objects themselves.
Also stay away from binding SQL connections in the session, as this also
can cause some nasty db access problems.
> Are there any guidelines/Best Practices discussing (or advocating) minimal use
> of HttpSession object as a placeholder for object data (ex. beans)?
If you are using the model2 jsp->servlet->jsp concept, then it's best to
bind objects to the request and forward(), and only bind to the session
for things that are constantly accessed, e.g. member's name, id, etc.
Any comments?
Andrew Beacock
Software Team Leader
InterVoiceBrite Ltd.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
