squid 开发的若干资料

关于开发Squid的ecap动态库插件的指导-About the development Squid ecap dynamic libraries plug guidance

http://blog.bbkanba.com/%E5%85%B3%E4%BA%8E%E5%BC%80%E5%8F%91squid%E7%9A%84ecap%E5%8A%A8%E6%80%81%E5%BA%93%E6%8F%92%E4%BB%B6%E7%9A%84%E6%8C%87%E5%AF%BC-about-the-development-squid-ecap-dynamic-libraries-plug-guidance/

Content Adaptation

http://wiki.squid-cache.org/SquidFaq/ContentAdaptation

Some adaptation mechanisms are limited in their scope. The following table summarizes what messages and what message partsthe mechanisms can adapt.

Mechanism

Request

Response

Header

Body

Header

Body

ICAP

yes

yes

yes

yes

Client Streams

yes

yes

eCAP

yes

yes

yes

yes

ACLs

yes

del

code hacks

yes

yes

yes

yes

Each adaptation mechanism has its strength and weaknesses. The following table attempts to rank mechanisms using frequently used evaluation criteria.

Evaluation Criteria

Mechanisms in rough order from "best" to "worst"

Squid independence

ICAP,eCAP, ACLs, Client Streams, code hacks

Processing speed

eCAP orClient Streams or ACLs or code hacks, ICAP

Development effort (header adaptation)

ACLs,code hacks, Client Streams, eCAP, ICAP

Development effort (content adaptation)

eCAP,ICAP, Client Streams, code hacks

Versatility

code hacks,eCAP, ICAP, Client Streams, ACLs

Maintenance overheads

ACLs,eCAP, ICAP, Client Streams, code hacks

http://code.google.com/p/squid-ecap-gzip/source/browse/trunk/squid-ecap-gzip/src/adapter_gzip.cc

http://www.e-cap.org/Documentation

http://code.google.com/p/squid-ecap-gzip/wiki/Installation

squid 部署

http://www.ibm.com/developerworks/cn/linux/l-cn-squid/

http://www.squid-cache.org/Doc/code/05_TypicalRequestFlow.html

http://www.squid-cache.org/Doc/code/05_TypicalRequestFlow.html

http://www.makelinux.net/alp/035

http://www.cs.cf.ac.uk/Dave/C/node27.html

http://markmail.org/message/5i65puksvx6muouy