Hi, Shai,
Thanks for the feedback - now that the refactoring is almost completed,
testing the extension mechanisms and fixing errors is the most
important thing for 3.3.
> I don't want to nudge too much, but I'm wondering what's going on with this.
> Correct me if I'm wrong, but the last (GREA
x27;reuse' code).
???
--Shai
-Original Message-
From: Shai Fultheim (BRM IL)
Sent: Saturday, December 30, 2000 21:25
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Session Serialize code
Thanks. I'll love to see this.
I'm rewriting the session seriali
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 for
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 r
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
PROTECTED]]
Sent: Friday, December 29, 2000 06:17
To: [EMAIL PROTECTED]
Subject: RE: Session Serialize code
I'll check in the fix tommorow - the HttpSessionBindingEvent and
session reloading should go into the facade22 module.
I was thinking about this - does it make sense to keep the sess
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
>> nee
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 lost.
>
>If the server crashes, then you are screwed either
on 12/29/2000 2:38 PM, "Kief Morris" <[EMAIL PROTECTED]> wrote:
> 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 lost.
If the server crashes, then you are screwed either way.
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
>> serializ
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 simpl
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 Mat
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 sess
}
> }
> stream.writeObject(results);
> } else {
> stream.writeObject(new Hashtable());
> }
> }
> }
>
>
>
> --Shai
>
> -Original
IL 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 :-)
I moved Jon's code to org.apache.tomcat.util.ObjectSerializer
( I removed all dependencies to Session o
Hi Shai,
Mea culpa :-)
I moved Jon's code to org.apache.tomcat.util.ObjectSerializer
( I removed all dependencies to Session or tomcat internals - it should
work for any serializable object ).
( my intentions were to make it more reusable and to reuse it in reloading
context attributes, etc -
16 matches
Mail list logo
