On Fri, 21 Nov 2003, Bruce Van Allen wrote: > My experience across about many different commercial and institutional > web servers leads me to at minimum wrap up all system-related actions -- > like file ops -- before printing output. And the best approach is: > output last. Otherwise, I find webservers inconsistent as far as when > they to let go of a CGI process. Perhaps someone who knows more about > Apache or IIS could comment.
Really? Interesting. I thought it was considered best to try to send back data early & often, and to flush output by setting $| to 1 -- the idea being that a script that takes a long time to produce results might lead to timeout errors if the web client gives up, but if you keep sending back data as it becomes available then the client will tend to keep the connection open. Have I had this wrong? Is it better to save up all output for the end? -- Chris Devers
