eCAP

An Introduction to eCAP

Asked by Jack Andrew

Hi,

I have managed to build an embedded Linux Kernel with libeCAP v0.0.3, ecap_adapter_sample v0.0.3, squid v3.1.19 installed. I am using this system as an HTTP proxy.

I have added each sample adapter using the notes found here:

http://wiki.squid-cache.org/Features/eCAP

I have checked cache.log and it tells me that the adapter modules have loaded correctly:
2012/11/01 02:06:06| Squid plugin modules loaded: 1
2012/11/01 02:06:06| Adaptation support is on
2012/11/01 02:06:06| Starting eCAP service: ecap://e-cap.org/ecap/services/sample/minimal
2012/11/01 02:06:06| Starting eCAP service: ecap://e-cap.org/ecap/services/sample/minimal
2012/11/01 02:06:06| Ready to serve requests.
2012/11/01 02:06:06| storeLateRelease: released 0 objects

I am unable to see exactly what each adaoter does? Do I need to turn them on somehow? How can I get some evidence that the adapters are working? Is there any documentation that I can use to help?

Thanks in advance,

Jack Andrew

Question information

Language:
English Edit question
Status:
Answered
For:
eCAP Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Alex Rousskov (rousskov) said : 		#1

What each adapter does is documented in the README file distributed with the adapter sample tarball. For example, the minimal adapter simply returns the message to the host application, without performing any adaptation (it is a simplest adapter we could write).

Please consider upgrading to libecap v0.2.0 (requires Squid v3.2) because earlier versions (and especially the corresponding Squid support) are buggy.

Can you help with this problem?

Provide an answer of your own, or ask Jack Andrew for more information if necessary.

To post a message you must log in.