On 1 Nov., 12:54, Gareth McCumskey <[email protected]> wrote:
> $this->getUser()->shutdown() == session_write_close();
>
> No need for both :)
>

hm in symfony 1.4.6 session_write_close(); is only called within the
shutdown function of sfSessionStorage class.
but not called from sfBasicSecurityUser->shutdown() nor from
sfUser.shutdown()
so I had to call it after $this->getUser()->shutdown()...

maybe a symfony change?





>
>
> On Mon, Nov 1, 2010 at 1:36 PM, axel at <[email protected]> wrote:
> > thx for your help:
>
> > adding:
>
> > $this->getUser()->shutdown();
> > session_write_close();
>
> > to the actions that usually take a long time (eg. pdf generation, xls
> > exports,...)
> > solved our problem
>
> > thx a lot!
>
> > On 1 Nov., 11:59, Gareth McCumskey <[email protected]> wrote:
> > > I wrote a blog post about this ages back. Feel free to take a look:
>
> > >http://garethmccumskey.blogspot.com/2009/10/php-session-write-locking...
>
> > > On Mon, Nov 1, 2010 at 12:26 PM, axel at <[email protected]> wrote:
> > > > hello,
>
> > > > when I start a symfony web request that needs several seconds to be
> > > > finished, other requests to the same server/symfony application sent
> > > > from the same client browser are "locked" until the first request is
> > > > finished. (requests started during the processing time of the first
> > > > long request that are sent from other clients (with other cookies and
> > > > client ips) are processed immediately.
>
> > > > is this a symfony configured behaviour (max parallel requests per
> > > > cookie or per ip?) or rather an apache config issue?
>
> > > > kind regards
> > > > axel
>
> > > > --
> > > > If you want to report a vulnerability issue on symfony, please send it
> > to
> > > > security at symfony-project.com
>
> > > > You received this message because you are subscribed to the Google
> > > > Groups "symfony users" group.
> > > > To post to this group, send email to [email protected]
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<symfony-users%[email protected]>
> > <symfony-users%[email protected]<symfony-users%[email protected]>
>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/symfony-users?hl=en
>
> > > --
> > > Gareth McCumskeyhttp://garethmccumskey.blogspot.com
> > > twitter: @garethmcc
>
> > --
> > If you want to report a vulnerability issue on symfony, please send it to
> > security at symfony-project.com
>
> > You received this message because you are subscribed to the Google
> > Groups "symfony users" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]<symfony-users%[email protected]>
> > For more options, visit this group at
> >http://groups.google.com/group/symfony-users?hl=en
>
> --
> Gareth McCumskeyhttp://garethmccumskey.blogspot.com
> twitter: @garethmcc

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to