On Thu, Feb 14, 2008, Amos Jeffries wrote:
I'm just checking 3.1 progress maps now that the current big patches are in.
Adrian: http://wiki.squid-cache.org/Features/LogDaemon
Can we add a timeline on this now please?
If it requires a push THN will provide a little funding to get it
Adrian Chadd wrote:
On Thu, Feb 14, 2008, Amos Jeffries wrote:
I'm just checking 3.1 progress maps now that the current big patches are in.
Adrian: http://wiki.squid-cache.org/Features/LogDaemon
Can we add a timeline on this now please?
If it requires a push THN will provide a little
On Fri, Feb 15, 2008, Amos Jeffries wrote:
Sorry if I was obtuse. I meant that you are the expert on this one. Are
you able to re-locate that mysterious branch and estimate when you will
have time to sync and push it to HEAD?
squid3_logdaemon
have you fixed the AddrInfo leak? :)
Adrian
On Thu, 2008-02-14 at 11:45 +1300, Amos Jeffries wrote:
http://wiki.squid-cache.org/Features/SourceLayout
Added ICMP to your list of components. It's a clear-cut one now.
Thank you. Can you lead this activity? We need somebody who will drive
the discussion and oversee actual changes...
1)
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 and
well today my colleges are discuss about the caching their very long
conversation their is 2 participants I am behalf of squid and others are
from BLUECOAT proxy sg hardware . well I am asking for squid developers
there is any solution on hardware based embedded with squid today the
marketing
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 Thu, 2008-02-14 at 11:45 +1300, Amos Jeffries wrote:
http://wiki.squid-cache.org/Features/SourceLayout
Added ICMP to your list of components. It's a clear-cut one now.
Thank you. Can you lead this activity? We need somebody who will drive
the discussion and oversee actual changes...
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 Thu, Feb 14, 2008, pokeman wrote:
well today my colleges are discuss about the caching their very long
conversation their is 2 participants I am behalf of squid ??? and others are
from BLUECOAT proxy sg hardware . well I am asking for squid developers
there is any solution on hardware
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
On Fri, 2008-02-15 at 12:24 +1300, Amos Jeffries wrote:
6) Should directory names use just_small, CamelCase, or CAPS
letters?
I Think CamelCase like we do for files and classes, with acroynms
being
upper case is working. When we can make the converted and re-used
legacy
files from
14 matches
Mail list logo
