perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <>
Subject Re: [Fwd: Re: The Byterange filter -- a new design -- feel free to rip it to shreds]
Date Mon, 02 Aug 2004 16:24:32 GMT
Geoffrey Young wrote:
> Stas Bekman wrote:
>>Catching up with httpd-dev: So should we adjust our docs/tests to strip
>>the input Range headers too, in addition to C-L in output filters? I'm
>>not quite sure I understand what are the circumstances when this needs
>>to be done.
> no, it is not required to strip Range at the moment - the short answer is to
> just forget about that thread :)
> the long answer is that the issue in the thread is that currently content
> handlers need to serve up all their content, even when byteserving, so that
> the byterange filter has all the data and can work.  the suggestion made in
> the thread is essentially to let content handlers (more specifically
> mod_proxy, which isn't a content handler) do the byteserving themselves, in
> which case they would need to let future filters know that only the
> specified Range is actually coming down the brigade, not the entire content
> for the request.
> to really get a feel for what is going on, see graham's response to one of
> my posts early in the thread
> this post seems to sum up where the thread was headed (and the dominant
> httpd-dev mindset) before it was restarted

I skimmed through the whole thread in first place, so I'm up to date :) 
But I was left with the impression that at the moment that wrowe was 
talking about the current situation:

> so basically, I wouldn't worry about Range at all, at least not at the
> moment - we may need to completely redesign our filter API if any of these
> proposed changes become real, but I really don't see that happening in the
> near future, certainly not with 2.0 and probably not even in 2.1.

OK, thanks Geoff.

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message