----- Original Message ----- From: "Perrin Harkins" <[EMAIL PROTECTED]> To: "Dodger" <[EMAIL PROTECTED]> Cc: "Modperl List" <[EMAIL PROTECTED]> Sent: Friday, April 16, 2004 10:52 AM Subject: Re: Autoflush without NPH...
> On Fri, 2004-04-16 at 13:37, Dodger wrote: > > Now, as long as PerlSendHeader is*On* will that make sure that it does NOT > > run as an NPH script if $! is set to 1? > > Do you understand what an NPH script is? It simply means that the > server is not parsing your output and adding headers, the way it > normally does when running under mod_cgi. Technically, all mod_perl > handlers and any Apache::Registry script run with PerlSendHeader off is > equivalent to an NPH script. Yep, of course. I've written several. At least half I've written won't work on IE because it won't do replace boundaries correctly. One was a nifty web-based MUD client, without so much as a hint of java or anything like that. > Turning autoflush on is not really part of it, but since people usually > are turning off header parsing in order to output something that > updates, it is a common practice. Buffering would kill things like > server-push, which was the main thing NPH scripts were used for. > > - Perrin All I have to go on is the documentation, which is noticably sparse in this area -- and DID indicate that turning autoflush on is really part of it. I got the impression that Apache::Registry does stuff when dealing with the script before running it, and I thought that it might possibly be doing some magic behind the scenes if it located $| being turned on. Anyway, I just tried it and it didn't seemto pay any attention to the vaue of $|. Seemed to block buffer everything anyway. -- Dodger -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
