Sorry, Kim, but why on earth you are polling with a second request to know when the first one has finished? I mean, when the first request inserts data in the database that's it, you'll manage the end of the request. $A ---> do stuff; do stuff; do stuff; report ready; $B ---> report ready? $B ---> report ready? $B ---> report ready? $B ---> report ready? report ready; ---> notification to A $B ---> report ready; the report ready, if it is when $A request has been finished, will be in $A, the polling via $B is absolutely useless, imo. There is no timeout from Ajax, it simply keep waiting, but obviously if your PHP has max_execution_time 30 seconds and the script execution takes more than 30 seconds there's no polling that could save you. The same if the user closes the browser, connection lost, bye bye response. To have a notice, you need Comet, try out Phico but still, a page that requires that much is not suitable for the web. Report creation should be a cronjob in a separed thread if it is that stressful. Regards > Date: Fri, 27 Mar 2009 10:47:10 -0400 > From: jbw2003@xxxxxxxxxxxxx > To: an_red@xxxxxxxxxxx > CC: php-general@xxxxxxxxxxxxx > Subject: Re: RE: flushing AJAX scripts > > My page submits the AJAX request to complete a report that takes some > time, and upon completion stores results in a database. A second AJAX > request polls every 5 seconds and queries the database if the report is > ready. This hopefully will get around any timeout problems I am having > with a long running request, and seems to be working. It looks like I > can accept the default behavior for now. I don't depend on getting a > response from the original request, but is there a point where the AJAX > response script will be stopped either by Apache or PHP before it can > insert into the database? > > Jim _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx
