Just wondering what the common methods of state management are available
for JSP developers. (Not looking for a generic answer, but items that are
very specific to JSP).
I belive ive seen talk of a session object/layer. How does this
work? non-persistent cookie? does it rely on this cookie 100%.
what about scaleability concerns? can this scale on a web farm easily and
properly? (not redirecting user back to same machine in the farm - but
being able to handle the request transparently across your entire
farm). Basically, where is this session information stored? Server memory
where the session started, database or other shared storage medium on a
per-user basis?
How are the sessions identified? some sort of GUID? How is this
generated, based on what criteria?
What are the limitations of this? That is, if we start loading this up,
how bad will it be for server performance? Anyone do any specific load
testing?
Thanks for any input.
===========================================================================
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
