httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: The Byterange filter -- a new design -- feel free to rip it to shreds
Date Tue, 13 Jul 2004 12:30:02 GMT
Joe Orton wrote:

> Yes, that's exactly what it's supposed to do already.  I haven't checked
> that it works via the proxy but it certainly does for other cases.

Ok, then most of the problem is solved :)

>>The full 650MB CD ISO is then transferred from the backend to the 
>>frontend, which then pulls out the bits the frontend needs dumping the 
>>rest. And this happens once for every single byte range request.

> And buffered into RAM each time too, nice.  This is another good case
> for the byterange filter not doing any work for anything other than
> "simple" content per my other mail.

I don't see where it would be buffered in RAM - proxy doesn't buffer 
much, and a byte range filter would either be passing data through, or 
dropping data on the floor. Unless I am missing something?

Regards,
Graham
--

Mime
View raw message