GENIUS! This worked perfectly. No, I was manually starting my sessions, but I didn't know about the blocking behavior. This now works perfectly.
Walter On Apr 8, 2007, at 4:50 AM, Fabian Lange wrote: > > Hi, > As the page is titled progress.php, I assume that your serverside for > both > actions is php? And I assume further that you use session autostart? > Then you are a bit in trouble because php is bad at what you want :) > One request blocks all other "threads" accessing the same session. > This can, to my knowledge, only be solved by the long running part > calling: > http://de.php.net/session_write_close > to indicate: I am done with the session anybody else can work on it. > > That works for me in 95% of the cases. In the rest 5% it despite that > gets > stuck and I haven't found a 100% solution > > .: Fabian > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
