This is a session issue. While a request is being processed, others from the same client (same sessionid) are held back to prevent simultaneous output to the session storage. In php, you can use session_write_close() to tell when you're finished writing to the session array (and php will start processing the next request in the background), in symfony there's the shutdown() function of sfUser.
On Mon, Nov 1, 2010 at 11:26, 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] > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- 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
