We have seperate actions that are called per "section" on our page and each "section" recieves seperate responses from the ajax calls to display its own data. This is also because each "section" periodically updates at different times
On Tue, Sep 15, 2009 at 2:18 PM, Sid Bachtiar <sid.bacht...@gmail.com>wrote: > > It's not Symfony, it's PHP session thing. But this issue is not unique > to PHP either. > > >> > Basically we have a few div's on one page that needs to be populated > >> > with > >> > the ajax returns. What seems to be happening though is instead of each > > You really need to just have one ajax call per event (e.g.: page load) > > On Wed, Sep 16, 2009 at 12:11 AM, Gareth McCumskey <gmccums...@gmail.com> > wrote: > > Thanks, looking at that link it seems to be exactly what we are > > experiencing. Would you know a way we could turn that session locking off > > within symfony? I am not too fond of the example given in that link. > > > > On Tue, Sep 15, 2009 at 1:57 PM, Sid Bachtiar <sid.bacht...@gmail.com> > > wrote: > >> > >> It is most likely due to PHP session locking: > >> http://nz2.php.net/manual/en/ref.session.php#64525 > >> > >> On Tue, Sep 15, 2009 at 11:45 PM, Gareth McCumskey < > gmccums...@gmail.com> > >> wrote: > >> > Hi all, > >> > > >> > We have encountered an odd problem that I believe should not be > >> > happening. > >> > Let me try and describe it as best I can. > >> > > >> > We have a symfony developed application using the Prototype javascript > >> > library. One of our pages (and others) make multiple ajax calls on > load. > >> > Basically we have a few div's on one page that needs to be populated > >> > with > >> > the ajax returns. What seems to be happening though is instead of each > >> > ajax > >> > call going to the server at the same time, we have the ajax calls > >> > queuing. > >> > What this means is that if one ajax call takes a long time to return a > >> > result (because of server load for example) all the other ajax calls > >> > wait > >> > until that item has recieved its response before they make their > >> > requests to > >> > the server. > >> > > >> > Even if, while these ajax elements are waiting for a response, the > user > >> > clicks another link to another part of the site, the browser will not > >> > load > >> > the new page until all the ajax calls are complete. > >> > > >> > We have thought of a number of possible causes but are struggling to > >> > figure > >> > out where this may happen. Is it the ajax itself that only allows one > >> > connection (client-side), the apache server limiting the number of > >> > connections per client, the PHP server only allowing processing of one > >> > request per client etc. > >> > > >> > Any insight to this problem would be greatly appreciated. > >> > > >> > -- > >> > Gareth McCumskey > >> > http://garethmccumskey.blogspot.com > >> > twitter: @garethmcc > >> > > >> > > > >> > > >> > >> > >> > >> -- > >> Blue Horn Ltd - System Development > >> http://bluehorn.co.nz > >> > >> > > > > > > > > -- > > Gareth McCumskey > > http://garethmccumskey.blogspot.com > > twitter: @garethmcc > > > > > > > > > > > -- > Blue Horn Ltd - System Development > http://bluehorn.co.nz > > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
