Personal tools
You are here: Home Products CacheFu Roadmap #1: Expand support for Squid configuration generation
Document Actions

#1: Expand support for Squid configuration generation

Contents
  1. Motivation
  2. Proposal
  3. Deliverables
  4. Risks
  5. Progress log
  6. Participants
by Justin Ryan last modified November 15, 2006 - 08:58
Support for optional features in squid.conf should be added / expanded.
Proposed by
Justin Ryan
Seconded by
Ricardo Newbery
Proposal type
Architecture
Assigned to release
Repository branch
trunk
State
being-discussed

Motivation

The current CacheFu is very helpful for getting the most basic Squid acceleration up and running, but does not address some more complex use cases such as:
  • using a pool of zeo clients as cache peers
  • caching dynamic content served out of Apache or another server in parallel
  • running the cache on a separate machine from Apache or Zope

Proposal

  1. Add support for cache_peer configuration with multiple Zeo clients
  2. Add support to squid.cfg for all occurrences of hardcoded 127.0.0.1 addresses

Deliverables

  • Improvements to existing squid.conf template
  • update to squid.cfg format for new options, i.e. squid version

Risks

This could increase the management overhead for Squid configuration templates.

Progress log

I have done some initial research and testing, but have nothing ready to commit as of yet.

Participants

Yes, I volunteer.


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by