> > Readbytes is only to be used by the filter that actually reads from the
> > network and the function that is requesting information. The function
> > that is requesting information (i.e. the top of the filter stack),
> > should insert either 0 or a positive value. 0 means read one line of
> > input, a positive value means read no more than this amount from the
> > network.
> >
> > The filter that is reading from the network should insert the number of
> > bytes read. All other filters should ignore this value. That's why this
> > used to be a field in the conn_rec, but at the hack-a-thon, it was
> > decided that this should be a parameter instead.
> >
> > The whole reason for this field, is that it is impossible to determine
> > when one request is done and another begins without information that is
> > stored in the request_rec.
>
> Umm. I don't see how this will work with SSL - the number of bytes read
> at the network layer does not correspond to anything happening at the
> request layer...
>
> Seems to me that this is being used to do something rather magical and
> protocol dependent...
Does SSL use a content-length? How does SSL know when the entire request
has been read?
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
