Hi,
>I see the advantage of using the HttpSession object to maintain session
>state, but would like to know if this has any adverse effect on
>scalability.
>Microsoft Active Server Pages 2.0 takes a big scalability hit when objects
>are stored as session variables. Can I safely assume Java's better
>threading
>support makes this a non-issue when developing JSPs and servlets?
That's a darn good question, and one I have been meaning to ask. It seems
odd to me that EJB, which I thought was partly being used to store sessions
(hence session beans) is much slower than using HttpSession to store session
state. I would love for someone to explain exactly why a session bean is
preferred not to be used for session state, and what makes it so slow
exactly. My only guess is that session state data is used frequently and
constantly going over the network to obtain it and/or modify it is what
makes it slow. IS the actual process of using EJB session (stateful) slow,
or is it the constant sending of data to/from the ejb session what makes it
slow?
Also, on that note, I also ask, is the HttpSession and web-server stuff
(servlets, action classes, javabeans, jsp, etc) scalable where you can add a
second web-server or more to handle more incoming requests, as well as can
two or more servers use the n-tier EJB servers properly? How does everything
stay in sync so that a 2nd web server that calls a 4th ejb server knows to
always send its requests to that 4th server, and how does the incoming
request for that session always know to go to the second web server so that
it can make sure it submits to the 4th ejb server?
Thanks.
===========================================================================
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
