Re^2: Using exit

Replies are listed 'Best First'.
Re^3: Using exit by geektron (Curate) on Dec 30, 2004 at 16:47 UTC
if you're trying to get things to display to the browser, there are other things to do: `$\|++;` [download] to force writes to be "immediate". (i'm forgetting the proper term .. not enough coffee yet this morning ... ) the reason `exit` is sending the output to the browser is because the write buffer is closed, like a `close` on a filehandle.	[reply] [d/l] [select]
Re^3: Using exit by revdiablo (Prior) on Dec 30, 2004 at 19:07 UTC
Take a look at merlyn's Watching long processes through CGI. It might be helpful.	[reply]
Re^3: Using exit by eieio (Pilgrim) on Dec 30, 2004 at 16:48 UTC
It sounds like you are developing a CGI application. If this is the case, turning off output buffering may ensure that the output from the script is displayed in the browser: `$\|++;` [download]	[reply] [d/l]
Re^4: Using exit by Anonymous Monk on Dec 30, 2004 at 16:52 UTC
Yes I am, and I am using $\|++ already, but at some point I would like to have what the exit does but no success yet.	[reply]
Re^5: Using exit by eieio (Pilgrim) on Dec 30, 2004 at 16:59 UTC
The behavior may be browser dependent. I've noticed that Safari on Mac OS X doesn't incrementally load pages even if the output buffering is disabled by the script. However, Firefox does incrementally display the page. While more complicated, a solution developed by Randal Schwartz may be more appropriate, if you are trying to provide incremental feedback during a long-running operation.	[reply]
Re^5: Using exit by geektron (Curate) on Dec 30, 2004 at 16:59 UTC
then you're between a rock and a hard place. you may need to refactor the output ... so that you're sending stuff more frequently ..... without seeing any code, that's probably the best any of us can do ...	[reply]


go ahead... be a heretic
	PerlMonks