[squid-users] e-CAP future development

I don't have a Launchpad account so I'll post my question here. I have been using SOPHOS SAVDI as an ICAP server for Squid for about 2 years (quite successfully). http://lists.squid-cache.org/pipermail/squid-users/2020-January/021620.html The problem is that SOPHOS SAVDI entered EOL and I can't rea

Re: [squid-users] e-CAP future development

Not sure what you are expecting to see. libecap just contains an API for passing HTTP message pieces between applications. HTTP high-level message structure has not changed since 2014. There is no reason for libecap to have changed.Amos___ squid-users mai

Re: [squid-users] e-CAP future development

On 1/2/23 08:56, Avram-Teodor Berindeie wrote: I would like to know what is expected regarding the further development of eCAP There are at least two changes that should happen to eCAP: 1. Removal of used-to-be-experimental C++ APIs from official declarations: https://bugs.launchpad.net/ecap/

[squid-users] e-CAP future development

So there will be a libecap 1.1 someday! In my environment I use ICAP and I hope to be able to use eCAP as well, but for that a new version of libecap would be good and of course the Clamav to solve the problem related to the scanning speed.

Re: [squid-users] e-CAP future development

On 1/2/23 13:44, Avram-Teodor Berindeie wrote: So there will be a libecap 1.1 someday! That is difficult to predict IMO. There should be libecap v2 someday, but whether that will actually happen, and whether there will be a v1.1 releas