>>> "Rajankar, Pankaj C-MS-PR" <[EMAIL PROTECTED]> 12-Jul-00 10:44:17
PM >>>
>He is correct.
>Those session variables highly affect scalablity.
False.
Session objects only affect scalability to the extent that you let
them.
I'm the architect for a web based email app that has over a million
us
"Godbey, David" wrote:
>
> A colleague of mine objects to using session objects to stash information
> because he claims it bloats the servlet environment. He prefers, instead, to
> stash the info in the cookie.
>
> What is the conventional wisdom on this?
My opinion is that enough people thought
>>> Gene Chuang <[EMAIL PROTECTED]> 12-Jul-00 11:02:21 PM >>>
>Fat sessions bloat the servlet environment and fat
>cookies jam the network pipeline. The best solution if
>you want to store large-sized session data is to have
>the Session object contain a primary key pointing to a
>database row.
>>> "Godbey, David" <[EMAIL PROTECTED]> 12-Jul-00 8:44:03 PM
>>>
>A colleague of mine objects to using session objects to
>stash information because he claims it bloats the servlet
>environment. He prefers, instead, to stash the info in the
>cookie.
>What is the conventional wisdom on this?
That
Hello,
He is correct.
Those session variables highly affect scalablity.
Cookies are fine if the information is not sensetive.
For crutial information consider the option of keeping the information in
database.
Regards.
Pankaj..
-Original Message-
From: Godbey, David [mailto:[EMAIL PROT
Hi,
Fat sessions bloat the servlet environment and fat cookies jam the network
pipeline. The best solution if you want to store large-sized session data
is to have the Session object contain a primary key pointing to a database
row.
Gene
-Original Message-
From: A mailing list for disc
> 1) As we're storing actual objects in the HttpSession object, if we use
> getValue and modify the object (properties) do we still need to use
> putValue? Why, aren't we dealing with another reference to the same object?
No need to use putValue. When you use getValue you are getting a
reference
# See Comments Below
(*Chris*)
- Original Message -
From: Chris Means <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 1999 12:24 AM
Subject: Session objects
> I'm just coming up to speed on this (Java & Servlets) so pardon me if the
> questions are silly.
>
>
On Tue, 13 Jul 1999, Chris Means wrote:
>
> 1) As we're storing actual objects in the HttpSession object, if we use
> getValue and modify the object (properties) do we still need to use
> putValue? Why, aren't we dealing with another reference to the same object?
We are storing object references
Shashank Phadke wrote:
>
> Hi --
>
> This can be extension to the question about where the session id is
> stored.
>
> Where do the servlet engines store the objects put into your session.
> Do they keep it in the VM memory ?? Or is it only part of the cookies
> sent to the browser ??
The session
> This can be extension to the question about where the session id is
> stored.
>
> Where do the servlet engines store the objects put into your session.
> Do they keep it in the VM memory ?? Or is it only part of the cookies
> sent to the browser ??
The servlet spec doesn't mandate how session i
11 matches
Mail list logo
