According to Dustin Tenney:
> > mod_perl ties the Perl STDOUT filehandle to Apache i/o, but this is
> > different from C stdout, which cannot easily hooked to Apache i/o without
> > a subprocess pipe (as mod_cgi does). I don't know of a decent workaround.
> > do you have access to the library sources?
>
> Yea I wrote the library. I was hoping to get this to work because I
> really need the extra performance that C is giving me. Basically it
> parses an html file and outputs the results to stdout. It uses
> open/read/write to do this. Is there any documentation anywhere on how
> this works? Thanks for the info.
Have you measured a performance difference here? I'd be very
surprised at anything you can do in C being enough faster at
doing something to an html file to make up for the process
startup time compared to letting mod_perl code do it - or
are you doing number crunching? Anyway if it is your own library
why not make it into a .xs module to get the speed without
having to start another process and hook its output? Or
if you do want the output, let your perl code read it from a
pipe or execute it in back-ticks.
Les Mikesell
[EMAIL PROTECTED]
