Eric,
I hope you can shed some light here! I understand how to use the
HttpSession object to maintain state. What I haven't been able to figure
out is how to maintain integrity. For example, in a http intranet
application using Java, Java Servlets, and JSP's, (and DB2/400), how do you
maintain session integrity? I have found the only way is to use
synchronized, but that slows down the app too much because virtually every
method changes the database objects. All the updating for a given request
must complete, and the object stored in the session, before the next
request can start.
I'm missing something basic here. I hope you can help!
Thanks in advance,
Phil
At 10:30 AM 1/17/00 , you wrote:
>Nikolas,
>I don't believe that what you are asking is possible. In particular, there
>is no way to keep
>the same session across two different browsers without requiring log-in,
>since cookies
>for both browsers are stored separately and IP addresses are not unique.
>
>In terms of spawning a new browser window, Netscape keeps the same session,
>so you can't
>invalidate one window in favor of the one "on top". In IE, there is
>actually a setting that allows
>you to choose whether or not a new window launches "in a separate process".
>Just check your
>Internet options -> Advanced tab -> Browsing ->
> Browse in a new process (IE4 ) or Launch browser windows in a separate
>process (IE5)
>
>Note that this setting is, by default, unchecked, so that most users should
>retain session across
>browser windows (the way Netscape does).
>
>I wouldn't worry too much about people using two different browsers for the
>same application -
>if people do this, they will probably be sophisticated enough to understand
>that the two sessions
>will be different. Amazon.com and many other Web sites work this way
>(different session under a
>different browser), so I wouldn't make this a technical or business
>requirement. This is something
>you should be able to explain to your colleagues.
>
>Same with browser windows - nobody expects when they open a new window to
>have the previous
>window go dead. In fact, I would see this as a bug.
>
>Asking for a unique ID for a GIVEN USER on a public Web application is not
>out of the question, though;
>many Web sites have this as an OPTION for the user, if he/she would like to
>take advantage of these
>session features (which you can promote on your site, as many other sites
>do). Simply have them
>choose a name and password, and kindly ask them to log in when they return
>(you can even
>remember their password via a cookie on the machine if they really want).
>By doing this,
>you are providing many features for little work on the user's part - and
>they can use ANY
>browser an ANY machine. And these days, people use more than one computer
>(at home,
>at work, Palm VII, etc), which makes you wonder about the usefulness of
>that PIII chip thingy.
>Also keep in mind that the number of people in this situation will only
>increase over time.
>
>Just some thoughts.
>
>Eric M. Andersen
>I/T Specialist
>IBM Global Services
>Tel: (781) 895-2637, Fax : (781) 895-2843, t/line : 362-2637
>Internet ID: [EMAIL PROTECTED]
>Lotus Notes ID: Eric M Andersen/Waltham/IBM
>
>===========================================================================
>To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
>JSP-INTEREST".
>FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
www.groschwitz.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
