Re: Output to Browser as script executes?

Why? Is it because you have a long running process and you want to provide updates as it runs, or is it because you are creating a page that is far too big to be sensible?

If it is dealing with a long running process that is the problem see replies to Long running CGI script and Managing a long running server side process using CGI.

True laziness is hard work

Comment on Re: Output to Browser as script executes?

Replies are listed 'Best First'.
Re^2: Output to Browser as script executes? by packetstormer (Monk) on Apr 05, 2012 at 10:41 UTC
It is mainly to keep the users informed. The actual process I will be running with the results of a user built template being passed to a mass SMS scheduler. There could be as little as 10 SMS text being sent or as many as 100,000. I would like the user to have some feedback on the result/status of the loop, if possible.	[reply]
Re^3: Output to Browser as script executes? by GrandFather (Saint) on Apr 05, 2012 at 10:49 UTC
In that case I'd be inclined to fork off a process to handle the scheduling task and return a page that has a timed refresh (include `<META HTTP-EQUIV="REFRESH" CONTENT="30">` in `<head>` for a refresh every 30 seconds for example) while the scheduling task is running. True laziness is hard work	[reply] [d/l] [select]