Re: Squid-3 roadmap change

On Wed, Sep 27, 2006, Henrik Nordstrom wrote:
> >> 1. Add minimal HTTP/1.1 support as a requirement for 3.0.STABLE. It's
> >> seriously starting to be a bigh hinderance for Squid being HTTP/1.0.
> >> At minimum we need chunked encoding and expect 100.
>
> > I dont agree - at the moment noone is developing or focusing this, and
> > we dont know how big an issue it is to implement. I'm worried this will
> > lead to an indefinite backoff effect.
>
> I obviously don't share this view of the complexity involved. Have
> implemented most of this already in 2.6 for a customer running Squid as a
> reverse proxy, and it's not really a big issue from what I have seen. The
> changes needed for minimal HTTP/1.1 level is

[snip]

> I am ok with that, just not so sure the world is..
>
> We are even more overdue in getting HTTP/1.1 support than the release of
> Squid-3.0.

I think its worth putting it and only it into Squid-3. Can you come up with
a diff or two implementing the required changes for review?

I do think its worth getting minimal HTTP/1.1 compliance into squid-3 as long
as we continue concentrating on repairing the current codebase before we
rush off and add even more features. :)

Adrian
Received on Wed Sep 27 2006 - 03:44:13 MDT