On Fri, 2004-04-16 at 14:25, Dodger wrote: > All I have to go on is the documentation, which is noticably sparse in this > area
You're welcome to improve it. NPH is not really a standard, just a common practice, and it's mostly irrelevant for mod_perl since you have complete control over your output, including headers. It's just a mod_cgi compatibility thing. > -- and DID indicate that turning autoflush on is really part of it. Turning on autoflush is something you do with perl to prevent it from buffering things. NPH is a server behavior from mod_cgi, so it can't really include anything perl-specific. Again, setting autoflush is just a common practice when writing NPH scripts in perl because of the way they are usually used. > 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. Nothing that I can recall. If you're curious about what Apache::Registry does, you can always look at the code. It's short, all in perl, and pretty easy to follow. > Anyway, I just tried it and it didn't seem to pay any attention to the value > of $|. Seemed to block buffer everything anyway. Turning on autoflush is enough to prevent perl/mod_perl from buffering. There is probably something else going on. - Perrin -- 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
