Re: [PATCH] Unbuffering slow CGI output

["Roy T. Fielding" <fi...@kiwi.ics.uci.edu>]

>That's because Roy's patch uses fileno(f) after various other actions have
>been performed on the FILE *.  This is a no no... the stdio stuff has
>stuff buffered at this point.  There is no quick fix, this whole cgi
>buffering thing requires some pretty extensive work imho. 

Yep, I thought that was going to be a problem.  I was hoping that the
fread buffer would not impact the stream for the later read.

>I want to turn the whole cgi thing into a select event loop with
>non-blocking descriptors.  It'll require help from buff.c to deal with
>problems like the above... and I'll probably ditch the use of FILE *
>completely.  That can hamper backwards compatibility.

It ain't worth it.  To do this right, we really need user-level STREAMS
like the IOStreams in Henrik's W3C libwww.  That is basically equivalent
to replacing all stdio with SFIO stacked disciplines.  Onward to 2.0.

....Roy

Re: [PATCH] Unbuffering slow CGI output

[Dean Gaudet <dg...@arctic.org>]

On Tue, 15 Jul 1997, Roy T. Fielding wrote:

> It ain't worth it.  To do this right, we really need user-level STREAMS
> like the IOStreams in Henrik's W3C libwww.  That is basically equivalent
> to replacing all stdio with SFIO stacked disciplines.  Onward to 2.0.

I was actually going to rip the similar code out of my mud... but you're
right, it isn't worth it.  The patch I posted a while back, which was against
Sameer's changes, essentially combines what you were trying to accomplish
with the BUFF changes necessary to support it.  I'll finish testing that
and repost it.

Dean