Re: HEAD squid3/errors/Armenian ERR_ESI,1.1,1.2 ERR_ICAP_FAILURE,1.1,1.2

2008-02-16 Thread Adrian Chadd
On Sat, Feb 16, 2008, Alex Rousskov wrote: > Another SourceForge HEAD commit? Such commits create problems for others > working with SourceForge CVS tree, right? Can we do something > simple/automatic to block these? Yes, there's a script run do to pre-commit checks (like our indent check) that s

Re: HEAD squid3/errors/Armenian ERR_ESI,1.1,1.2 ERR_ICAP_FAILURE,1.1,1.2

2008-02-16 Thread Alex Rousskov
On Fri, 2008-02-15 at 14:05 +, Arthur Tumanyan wrote: > Update of cvs.devel.squid-cache.org:/cvsroot/squid/squid3/errors/Armenian > > Modified Files: > ERR_ESI ERR_ICAP_FAILURE > Log Message: Another SourceForge HEAD commit? Such commits create problems for others working with SourceFo

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Alex Rousskov
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

Re: cvs commit: squid/src/fs/diskd store_io_diskd.c

2008-02-16 Thread Adrian Chadd
On Sat, Feb 16, 2008, Guido Serassio wrote: > > Bugzilla #761 : Handle recursive completion operations in diskd. > > I think that probably this should be also committed to SQUID_3_0. Yes, once I've looked at how to do it. The code's slightly different.. Adrian

Re: cvs commit: squid/src/fs/diskd store_io_diskd.c

2008-02-16 Thread Guido Serassio
Hi, At 13:39 16/02/2008, Adrian Chadd wrote: adrian 2008/02/16 05:39:33 MST Modified files: src/fs/diskd store_io_diskd.c Log: Bugzilla #761 : Handle recursive completion operations in diskd. I think that probably this should be also committed to SQUID_3_0. Regards Gu

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Tsantilas Christos
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 i

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Adrian Chadd
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

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Tsantilas Christos
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 abo

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Adrian Chadd
On Sat, Feb 16, 2008, Tsantilas Christos wrote: > > Wrapper calls most probably do have some penalties. With increasing > > delays on back-compat wrappers-on-wrappers as time (and changes) go by > > if they are not culled out. > > The wrapper calls normally have a minimal penalty. But depending

Re: eCAP: expose Squid or link with eCAP lib?

2008-02-16 Thread Tsantilas Christos
Hi Amos, Amos Jeffries wrote: > 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 muc