Re: protocol clarity

2006-10-10 Thread Alex Rousskov
On Sun, 2006-09-10 at 21:40 +1000, Robert Collins wrote: So I've finished my analysis of the protocol stuff in squid - protocol_t etc. http://wiki.squid-cache.org/ForwardRework has some thoughts about how we can improve the current api, to make SSL fit in more cleanly, and make doing some

Re: protocol clarity

2006-10-10 Thread Robert Collins
On Tue, 2006-10-10 at 09:24 -0600, Alex Rousskov wrote: On Sun, 2006-09-10 at 21:40 +1000, Robert Collins wrote: So I've finished my analysis of the protocol stuff in squid - protocol_t etc. http://wiki.squid-cache.org/ForwardRework has some thoughts about how we can improve the

Re: protocol clarity

2006-10-10 Thread Alex Rousskov
On Wed, 2006-10-11 at 11:54 +1000, Robert Collins wrote: http://wiki.squid-cache.org/ForwardRework I haven't considered icap deeply. In terms of forwarding icap is mostly/nearly orthogonal. There are things we handle that are not icap interceptable - but perhaps they should be. (For

Re: protocol clarity

2006-10-10 Thread Adrian Chadd
On Tue, Oct 10, 2006, Alex Rousskov wrote: P.S. I wonder if FreeBSD netgraph API is worth studying in this context! That, and the BBC Kamelia framework. It doesn't (or didn't) cover structured data representations IIRC and focused purely on shoveling data between modules but I think its

protocol clarity

2006-09-10 Thread Robert Collins
So I've finished my analysis of the protocol stuff in squid - protocol_t etc. http://wiki.squid-cache.org/ForwardRework has some thoughts about how we can improve the current api, to make SSL fit in more cleanly, and make doing some nifty things, like forwarding via ssh tunnels, or peers that