[Seaside] Fatal Flaw in my Web App!

[Norbert Hartl]

On Fri, 2008-05-23 at 17:32 -0300, Sebastian Sastre wrote:
> ...and that's why we use connection pools for those sessions right?
> 
The main objective to use the pools is to save connections. As databases
are getting slower with increasing number of connections you should
think about keeping them low. As Ramon said, database sessions aren't
tied to connections so a pool is good to achieve it. I have 10
images running with each of them having approx. 2 connections open.
Btw. the connection pool is also a protection against stalled
connections.

Norbert
> Sebastian Sastre
> 
>  
> 
> > -----Mensaje original-----
> > De: seaside-bounces at lists.squeakfoundation.org 
> > [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> > de Boris Popov
> > Enviado el: Viernes, 23 de Mayo de 2008 16:48
> > Para: Seaside - general discussion
> > Asunto: RE: [Seaside] Fatal Flaw in my Web App!
> > 
> > ... which of course won't make it run any sooner. The registry is
> > configured to expire handlers according to 
> > #shouldCollectHandlers and if
> > user closes their browser without clicking your logout button which
> > immediately sends #expire to the session, it will still be subject to
> > the same cleanup conditions.
> > 
> > -Boris
> > 
> > -- 
> > +1.604.689.0322
> > DeepCove Labs Ltd.
> > 4th floor 595 Howe Street
> > Vancouver, Canada V6C 2T5
> > http://tinyurl.com/r7uw4
> > 
> > boris at deepcovelabs.com
> > 
> > CONFIDENTIALITY NOTICE
> > 
> > This email is intended only for the persons named in the message
> > header. Unless otherwise indicated, it contains information that is
> > private and confidential. If you have received it in error, please
> > notify the sender and delete the entire message including any
> > attachments.
> > 
> > Thank you.
> > 
> > > -----Original Message-----
> > > From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> > > bounces at lists.squeakfoundation.org] On Behalf Of Sebastian Sastre
> > > Sent: Friday, May 23, 2008 12:40 PM
> > > To: 'Seaside - general discussion'
> > > Subject: RE: [Seaside] Fatal Flaw in my Web App!
> > > 
> > > Hi Richard,
> > > 
> > > 	I'm overriding #expire in a custom session class to free
> > resources
> > > (like
> > > persistence sessions).
> > > 
> > > 	cheers,
> > > 
> > > Sebastian Sastre
> > > 
> > > 
> > > 
> > > 
> > > 
> > > > -----Mensaje original-----
> > > > De: seaside-bounces at lists.squeakfoundation.org
> > > > [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> > > > de Richard K Eng
> > > > Enviado el: Viernes, 23 de Mayo de 2008 16:31
> > > > Para: Seaside - general discussion
> > > > Asunto: Re: [Seaside] Fatal Flaw in my Web App!
> > > >
> > > > I have a puzzling problem. I've made some changes to do what
> > > > you suggest.
> > > > I've subclassed WASession:
> > > >
> > > > WASession subclass: #GSSession
> > > >
> > > > ...with instance variable #database. I've created
> > > > #unregistered as follows:
> > > >
> > > > unregistered
> > > >     database ifNotNil: [database logout].
> > > >     super unregistered
> > > >
> > > > I've put the following in #GSRegistrationLogin (my root
> > > > component for the
> > > > app):
> > > >
> > > >     self application preferenceAt: #sessionClass put: GSSession
> > > >
> > > > And when the user logs out, the following is executed:
> > > >
> > > >     html anchor
> > > >         callback: [self session expire];
> > > >         with: [html paragraph style: 'color: red'; with:
> > > > [html strong:
> > > > 'Logout']]
> > > >
> > > > But the #unregistered doesn't always get executed. Sometimes,
> > > > not at all!
> > > > And sometimes, much later, as in the *next* time I login and
> > > > logout (?!).
> > > > What am I doing wrong?!! Shouldn't session expiry *always* cause
> > > > #unregistered to execute?
> > > >
> > > > Thanks,
> > > > Richard
> > > >
> > > > ----------------
> > > > John wrote:
> > > >
> > > > I usually store my glorp session on the seaside session, and upon
> > > > expiring, it sends logout to the glorp session.
> > > >
> > > > This has the dual benefit of the above, and having easy 
> > accessor to
> > > > glorp in the form of:
> > > >
> > > > self session glorpSession
> > > >
> > > > anywhere in my Tasks/Components.
> > > >
> > > > John
> > > >
> > > > _______________________________________________
> > > > seaside mailing list
> > > > seaside at lists.squeakfoundation.org
> > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> > > 
> > > _______________________________________________
> > > seaside mailing list
> > > seaside at lists.squeakfoundation.org
> > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> > _______________________________________________
> > seaside mailing list
> > seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside