input filters / getline (was: Re: SSL support)

[Greg Stein <gs...@lyra.org>]

On Sun, Feb 04, 2001 at 04:53:19PM -0800, rbb@covalent.net wrote:
> > > I think it's a bad design :-) ... but am not ready to spend the time on it
> > > to suggest an alternative. IMO, the input filters should always read chunks
> > > of data. The upper filters can massage that into lines, if that is what is
> > > needed.
> > 
> > Right. The obvious way out of this is to provide general purpose brigade
> > masseurs (or masseuses) that will give you a line from a chunky brigade.
> > But perhaps I'm missing something.
> 
> What you are missing is how to get the data back to the lower
> filter.  Right now, filters are one way, if we have a set of functions
> that break data, we need to send that data back to the bottom of the
> filter chain, otherwise it won't be there for the next request.

The key here being that if a *request* input filter reads in a chunk,
extracts a line, determines "end of request", then how does it get it put
back for the next request to deal with it?
[ it can't just cache it for later ]

This (presumably) isn't a problem for connection filters.
[ since these *can* cache it for the next request to read ]

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/