Re: Simplest Ajax/Comet style way to avoid client timeouts in a slow request

On Dec 20, 11:10 am, Tim Streater <timstrea...@xxxxxxxxxxxx> wrote:

In article <0c1f4a60-3f8e-46df-b4c6-6e281093a...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,

[..]

What is the result status the result *of* ?  Does it need to come
*after* the report is run? Since that report is going to e-mail,
what about sending the status before doing the report?

--
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

Hi Tim, many thanks for your prompt reply. The final result ststus
is one of "OK - email sent" or "Error - failed to send email".

But how the server completes the request isn't really relevant - It
could just as well return formatted HTML for the web app to display,
as for a normal POST/response cycle.

The only problem is the time the server takes to fulfill the request,
which is why I think it needs to be done via Ajax with intermediate
"still working on this ..." pings from the server.

Or is there a simpler way for the browser client to reset the client
timeout every few seconds, for example with a periodic Javascript
timed alarm? That would be even better.


Cheers

John R Ramsden
.

Quantcast