× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Servlet Session Information
  • From: "Clapham, Paul" <pclapham@xxxxxxxxxxxxx>
  • Date: Mon, 16 Oct 2000 08:18:27 -0700

Since this information consists of Java objects, it's most likely that it's
stored in the memory used by the server.

-----Original Message-----
From: Robert Kraai [mailto:rkraai@KNITRITE.COM]
Sent: October 14, 2000 03:17
To: JAVA400-L@midrange.com
Subject: Servlet Session Information


Where exactly does the Servlet store the HttpSession information when I
create a session object?  I believe it is on the server side and mapped to
with the session ID of the client (but please correct me if I am wrong).  So
where exactly would that be on the server?  I also believe that it is
dependant on what application server I am using, since it is part of the
Servlet API...

I did some looking to see what exactly changed when I executed the following
code in a simple doGet method, and I seem to be unable to find it.

HttpSession httpSession = httpRequest.getSession(true);
httpSession.putValue("Productnumber", "Product1");

Just curious...
---Bob
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.