On 12/29/00 6:35 PM, "Jon Stevens" [EMAIL PROTECTED] wrote:
If the server crashes, then you are screwed either way.
If you are live, then serializing/deserializing the sessions for each and
every request could be a major slowdown (even with this code). This is why
there still isn't a good
On 12/30/00 6:00 AM, "Kief Morris" [EMAIL PROTECTED] wrote:
It doesn't need to. I'm writing PersistentManager to put the session
on a queue to be serialized by another thread. This shouldn't have a
noticeable performance impact.
At least on a machine that is not totally tweaked out and
On Sat, 30 Dec 2000 [EMAIL PROTECTED] wrote:
Thanks. I'll love to see this.
I'm rewriting the session serialize code as a plug-in module (that was your
offer), so I need sterilization support for ServerSession.
Please take care of that as fast as you can.
I'm working on it - sorry
on 12/30/2000 6:00 AM, "Kief Morris" [EMAIL PROTECTED] wrote:
Jon Stevens typed the following on 06:35 PM 12/29/2000 -0800
I can see this being used for fault tolerance. If your servlet engine
crashes,
or if you have to restart it for some reasons, your users' sessions don't
need
to be
Thanks. I'll love to see this.
I'm rewriting the session serialize code as a plug-in module (that was your
offer), so I need sterilization support for ServerSession.
Please take care of that as fast as you can.
--Shai
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED
Hi Guys,
I worked quite a bit with apache serialization code a several months back on
various VM's speeding it up. I think I have several observations that I
hope you'll consider before using the code I just saw fly by on the list.
Basically, I'm a proponent of using externalizable for the
on 12/29/2000 6:59 AM, "Matthew Dornquast" [EMAIL PROTECTED] wrote:
Anyway, use this method, and you've got lean mean serialized objects that
take up the least amount of space possible and have the lowest overhead to
serialize/deserialize.
Warm regards,
-Matthew
Fuck ya! Go Matthew.
Matt, since they are considering a threadpooler, too, you might also want
to share your Object and Thread pooling techniques you've done in the
past. The design alone is worth considering it over other
techniques. (Matthew has a pooling demo using Object.clone(), which is
also very fast and
Jon Stevens typed the following on 12:16 PM 12/29/2000 -0800
on 12/29/2000 6:59 AM, "Matthew Dornquast" [EMAIL PROTECTED] wrote:
Anyway, use this method, and you've got lean mean serialized objects that
take up the least amount of space possible and have the lowest overhead to
Hi Costin,
As discussed a week ago, someone took out Jon's code to serialize session
from 3.3.
That code was part of 3.2 but does not exist in 3.3. Could you please add it
back into ServerSession??
As proposed by you I'm working on "SerializableSession" module, and I need
that piece of code to
{
stream.writeObject(new Hashtable());
}
}
}
--Shai
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 29, 2000 03:24
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Session Serialize code
Hi Shai,
Mea culpa
11 matches
Mail list logo
