Rakesh Bhat wrote:
>
> 1.IS session handling a must process in all web applications ?
No, but the question is how would you pass information between other
web-app participants ?
This is one of the simplest, fastest way to deal with parameters (aka
attributes) of web-app, so what else to expect in order to begin using
it ?
> 2.If not ,how does one has to decide whether he/she has to handle session tracking in
> the application ? or is it a good practice to handle session tracking in all web
> applications ?
Actually, the answer on the above question is on that too. Just think
about passing configuration parameters, any other settings. Even though
you could come up with some other solution, but these wouldn't beat
session when speed matters (always does actually:). Sometimes however
it's not possible to use session (cookies are disabled or URLRewritting
is not an option). You could just put all the information in HTML page
as FORM hidden fields, but that's very risky as an user can create a
page with wrong data which could expose bad application behaviours (i.e.
crashes:).
Take a look at some examples described in Java documentation
(http://java.sun.com/j2ee) and you'll see it's not easy to *not* use
session.
> Rakesh.
Jacek Laskowski
===========================================================================
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
