#4: Improve support for varying squid versions

Contents
  1. Motivation
  2. Proposal
  3. Implementation
  4. Deliverables
  5. Risks
  6. Progress log
  7. Participants
by Justin Ryan last modified Jan 22, 2010 06:25 AM

We should support Squid 2.6 and possibly Squid 3.0 and even some older versions of Squid.

Proposed by
Justin Ryan
Seconded by
Balazs Ree
Proposal type
Architecture
Assigned to release
Repository branch
bitmonk-squid-2.6
State
in-progress

Motivation

The current squid config generator works with version 2.5STABLE6 up to 2.5STABLE14, but nothing newer or older.  This code is no longer the newest or fastest, and some commercial OS distributions provide slightly older code, i.e. 2.5STABLE3, which we are not compatible with.

Proposal

Our template needs to be able to generate configuration and helper scripts tailored to perform optimally with a given squid version.

Implementation

  1. Add a version option to squid.cfg
  2. Add conditional code in our squid.conf and other templates which decides how to generate config based on version

Deliverables

A squid config template which generates OOTB working config for:

  • Squid 2.5STABLE3
  • Squid 2.5STABLE6-14
  • Squid 2.6
  • Squid 3.0 ?

Risks

This could make the squid template(s) more difficult to maintain.

Progress log

  • I have a working configuration and test setup for 2.6STABLE3 which may even be 3.0-compatible and performs much better than the old config in 2.5.
  • There are untested changes to the config templates in a branch, feedback welcome.

Participants

Justin Ryan

Comments (1)

Justin Ryan Nov 14, 2006 09:35 PM
This is being done in tandem with http://plone.org/products/cachefu/roadmap/1 .