Re: cvs commit: squid3 configure.in

On Mon, 2007-08-27 at 07:37 -0600, Henrik Nordstrom wrote: > hno 2007/08/27 07:37:02 MDT > Log: > Enable HTCP and SNMP support by default in the binary, but default off in > squid.conf Should we enable ICAP in the binary by default as well? It is probably nearly as widely used as HTCP

Re: docs squid3/src/DiskIO/AIO AIODiskFile.cc,1.4,1.4.2.1 AIODiskFile.h,1.2,1.2.14.1

On Sat, 2007-08-25 at 03:23 +, Amos Jeffries wrote: > Update of cvs.devel.squid-cache.org:/cvsroot/squid/squid3/src/DiskIO/AIO > > Modified Files: > Tag: docs > AIODiskFile.cc AIODiskFile.h > Log Message: > BUG: silent implicit type conversion. found by doxygen. > > > Index: AIO

Re: cvs commit: squid3 configure.in

On tor, 2007-09-06 at 10:00 -0600, Alex Rousskov wrote: > On Mon, 2007-08-27 at 07:37 -0600, Henrik Nordstrom wrote: > > hno 2007/08/27 07:37:02 MDT > > Log: > > Enable HTCP and SNMP support by default in the binary, but default off in > > squid.conf > > Should we enable ICAP in the b

Re: Enabling ICAP by default

On Thu, 2007-09-06 at 20:29 +0200, Henrik Nordstrom wrote: > On tor, 2007-09-06 at 10:00 -0600, Alex Rousskov wrote: > > On Mon, 2007-08-27 at 07:37 -0600, Henrik Nordstrom wrote: > > > hno 2007/08/27 07:37:02 MDT > > > Log: > > > Enable HTCP and SNMP support by default in the binary, b

Re: Contribution to Squid development.

pointer to the > very same structure. > > Among the promised new features, only SASL bind has been added and > (partially) tested (only EXTERNAL with ldapi:// right now; more will > follow). It either uses parameters passed by command-line or defaults > set via ldap.conf/ldaprc

Re: cvs commit: squid3 configure.in

On Thu, Sep 06, 2007, Henrik Nordstrom wrote: > Maybe. I'll leave that to you to judge. Don't have a clear opinion > either way. But why not? > > HTCP and SNMP is very non-intrusive, just enabling code which is never > used unless configured in squid.conf, with no significant change in > other co

Re: cvs commit: squid3 configure.in

Adrian Chadd wrote: > Ok, how's that work for exposing C++ interfaces in Squid to external > modules? Things could get quite ugly if you're going C++ -> C -> C++.. Perhaps I was unclear. There's no C++ -> C -> C++; the only C step is module_init(), which is called when the module is loaded and r

Re: cvs commit: squid3 configure.in

On Fri, Sep 07, 2007, Pierangelo Masarati wrote: > Adrian Chadd wrote: > > > Maybe one of the goals for squid-3.1 should be runtime loadable dyanmic > > modules for "stuff". > > > > (Although I'm not sure how well that'd work with C++ and its symbol > > munging..) > > I've some experience in thi

Re: cvs commit: squid3 configure.in

Adrian Chadd wrote: > Maybe one of the goals for squid-3.1 should be runtime loadable dyanmic > modules for "stuff". > > (Although I'm not sure how well that'd work with C++ and its symbol > munging..) I've some experience in this sense, . Initially, I was set