On Sat, 2008-02-23 at 15:03 +0100, Henrik Nordström wrote:
fre 2008-02-15 klockan 09:07 +1100 skrev Robert Collins:
Its more work both at code and at runtime. The only thing it really
allows that 1) doesn't is non-GPL eCAP modules.
I don't see how 2) can allow non-GPL eCAP modules. We
tor 2008-02-14 klockan 09:09 -0700 skrev Alex Rousskov:
1) Expose Squid internals: Publish/install Squid headers and
libraries to give direct access to Squid resources. This
approach will most likely require installing pretty much all
headers because the module
fre 2008-02-15 klockan 09:07 +1100 skrev Robert Collins:
Its more work both at code and at runtime. The only thing it really
allows that 1) doesn't is non-GPL eCAP modules.
I don't see how 2) can allow non-GPL eCAP modules. We can't add a
linking excemption to the license even if there is a
Hi Adrian,
Adrian Chadd wrote:
On Sat, Feb 16, 2008, Tsantilas Christos wrote:
.
PS. I actually believe that it must exists a squid external utility
library which will be used by both squid and modules. But OK this looks
difficult right now...
Its been talked about for
On Sat, Feb 16, 2008, Tsantilas Christos wrote:
OK, but this is not a requirement, squid3 is enough good without it. And
become better day by day. There is significant progress.
I started working on this in my Squid-2 branch; this upset some people. :)
It is not that it will upset some
Adrian Chadd wrote:
Hey, I'm happy if Squid development was aligned with what our diverse
group of users wants. But thats a discussion going on the squid-core list;
OK men no problem, you can do yours discussions in squid-core list...
I was just answered an email which has my mail address in
On Sat, 2008-02-16 at 12:20 +0200, Tsantilas Christos wrote:
PS. I actually believe that it must exists a squid external utility
library which will be used by both squid and modules. But OK this looks
difficult right now...
That is exactly what eCAP library will do, I think. Both Squid and a
Hi,
Alex Rousskov wrote:
1) Expose Squid internals: Publish/install Squid headers and
libraries to give direct access to Squid resources. This
approach will most likely require installing pretty much all
headers because the module may need to use many Squid
Tsantilas Christos wrote:
Hi,
Alex Rousskov wrote:
1) Expose Squid internals: Publish/install Squid headers and
libraries to give direct access to Squid resources. This
approach will most likely require installing pretty much all
headers because the module may
On Fri, 2008-02-15 at 09:07 +1100, Robert Collins wrote:
On Thu, 2008-02-14 at 09:09 -0700, Alex Rousskov wrote:
An eCAP loadable module needs to plug into Squid message processing
pipeline, similar to how ICAP servers do that now, but without ICAP/TCP
overheads. I see two design choices
Hello,
The Squid eCAP branch already has limited support for loadable
modules. I have also written some eCAP-specific code, but I am not
satisfied with its design yet. This may be the last opportunity to
change things without rewriting a lot of code so I would love to get
your feedback
On Fri, 2008-02-15 at 12:15 +1300, Amos Jeffries wrote:
I imagine the basic first-signup users of eCAP will be wanting to
perform content-filters on pages as they arrive. That only needs a
read-only buffer of the page data and a hook to allow/deny the
transaction.
FWIW, some of the users
On Fri, 2008-02-15 at 12:15 +1300, Amos Jeffries wrote:
I imagine the basic first-signup users of eCAP will be wanting to
perform content-filters on pages as they arrive. That only needs a
read-only buffer of the page data and a hook to allow/deny the
transaction.
FWIW, some of the users
On Fri, Feb 15, 2008, Amos Jeffries wrote:
I'd choose (3). Some of the basic types have clean headers already.
Is it possible to incrementally grow eCAP access to the internals of
squid? Starting with, ie just a buffer of page text, and work the API up?
I mean, we publish the available
14 matches
Mail list logo
