Menu
Community /Pin to ProfileBookmark
@NogDogJun 19.2008 — #I do not know if there is some way to address it in that manner.
I'd probably consider putting the while loop into the client side JavaScript, and simply have the server side PHP script return the continue no/yes response as part of the result data so that the JavaScript can then decide whether or not to request it again or process the result. @NogDogJun 19.2008 — #Just a thought: what would happen if you output a space or newline every few seconds within the loop, possibly followed by a flush() to encourage the web-server to send it immediately rather than buffering it? @NogDogJun 19.2008 — #
I don't think the problem was the amount of data, but rather the loop that waits until something else (apparently) changes something in the database to the desired value.
PHP Header for Timeout?
I am programming an AJAX web application, but I am encountering a potential problem regarding timeouts. Some browsers (notably Safari) will “wait” only 1 minute for a request to be sent back from PHP. Here is a bit of my code:
[code=php]$initquery = “select * from MyTable…”; // a MySQL query
do{
sleep(1);
$result = mysql_query($initquery);
$result = mysql_fetch_assoc($result);
}while($result[“continue”]==”no”);
The code works fine. The problem is, if [FONT=”Courier New”]$result[“continue”][/FONT] does not change to “yes” within a minute (this is done by other scripts), the browser will stop waiting and issue a timeout error. Is there a way to make the browser wait longer for a response? I was thinking that this could be done with some kind of header that sets timeout at five minutes or something (like [FONT=”Courier New”]header(‘Cache-Control: no-cache, must-revalidate’);[/FONT] makes the browser not cache the page). Is this possible? Thanks in advance.
[COLOR=”White”].
Sign in
to post a comment6 Comments(s) ↴
0
@NogDogJun 19.2008 — #I'd probably consider putting the while loop into the client side JavaScript, and simply have the server side PHP script return the continue no/yes response as part of the result data so that the JavaScript can then decide whether or not to request it again or process the result.
0
@NogDogJun 19.2008 — #0
@NogDogJun 19.2008 — #If your making a request for data that is taking more than a minute in response time, ho much data are you requesting in the first place?
AJAX is bes used for small file requests like text files.
My suggestion is to break your data down into manageable chunks that take seconds to deliver rather than minutes. With that type of interface, how do you ever hope to retain visitors? Waiting around for 5 minutes for a web page is not my idea of phun.[/QUOTE]
I don't think the problem was the amount of data, but rather the loop that waits until something else (apparently) changes something in the database to the desired value.