[squid-users] content adaptation using squid
eliezer at ngtech.co.il
Fri Sep 7 09:29:28 UTC 2018
The list of the known ICAP servers that I can list are:
- echelon-mod (Which I wrote from 0 but is not public)
I wrote both eCAP and ICAP services/modules code and I found it very easy to start with an ICAP service.
Then and only if the ICAP service seems to make sense and works as expected try to asses either:
- eCAP module
- Proxy Service
- Other creative idea
I have worked couple years ago on a tproxy based p2p caching software but eventually erased the code...
It's nice to have some cash from cache but I like my green/white hat rather then the black one.
All The Bests,
Linux System Administrator
Email: eliezer at ngtech.co.il
From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] On Behalf Of Alex Rousskov
Sent: Thursday, September 6, 2018 7:46 PM
To: squid-users at lists.squid-cache.org
Subject: Re: [squid-users] content adaptation using squid
On 09/06/2018 12:06 AM, Yosef Meltser wrote:
> In contrast to the above, ECAP is not using any server, and the whole
> process in embedded into the squid, so it sounds quite easier. Is it?
Overall, there is no drastic complexity difference between
* embedding your code into an ECAP-capable host like Squid and
* embedding your code into an ICAP server like c-icap.
In some cases, even the APIs are going to be similar! Some ICAP servers
are probably easier to work with than eCAP, and some are probably more
cumbersome, but you are doing the same work on the conceptual level --
writing a "plugin" where your adaptation code/logic lives.
An ICAP server introduces an additional stand-alone service/software
that you have to take care of, of course.
Needless to say, writing an eCAP adapter is much easier than writing a
(good) ICAP server -- writing an ICAP server from scratch is usually the
squid-users mailing list
squid-users at lists.squid-cache.org
More information about the squid-users