Re: Introduction and new eCAP GZIP adapter
Constantin Rack wrote: Dear squid-dev members, my name is Constantin Rack and I would like to introduce myself as a new developer. I have over 10 years experience in C/C++ coding with strong focus to HTTP related software. As a welcome gift, I have released a new open-source eCAP adapter for HTTP compression: http://www.vigos.com/products/eCAP/ I would like to maintain and further develop this adapter, hoping that it will be included in the official SQUID distribution some day. Please feel free to send me your suggestions and bug reports concerning the adapter. A happy 2009 everyone! Best Regards, Constantin Rack With a welcome gift like that I'm sure we're all eager to see whats next ;-) Welcome ;-)
Re: Introduction and new eCAP GZIP adapter
On Mon, Jan 5, 2009 at 7:12 PM, Constantin Rack constantin.r...@vigos.com wrote: Dear squid-dev members, my name is Constantin Rack and I would like to introduce myself as a new developer. I have over 10 years experience in C/C++ coding with strong focus to HTTP related software. As a welcome gift, I have released a new open-source eCAP adapter for HTTP compression: http://www.vigos.com/products/eCAP/ I would like to maintain and further develop this adapter, hoping that it will be included in the official SQUID distribution some day. Please feel free to send me your suggestions and bug reports concerning the adapter. Hi Constantin, you may want to register your module with the newly-created Third Party Modules Registry (for lack of a better name), until the time of the official inclusion comes. You can find it at http://wiki.squid-cache.org/ThirdPartyModules Thanks, welcome, and good work! -- /kinkie
Re: Introduction and new eCAP GZIP adapter
As a welcome gift, I have released a new open-source eCAP adapter for HTTP compression: http://www.vigos.com/products/eCAP/ I would like to maintain and further develop this adapter, hoping that it will be included in the official SQUID distribution some day. Please feel free to send me your suggestions and bug reports concerning the adapter. Hi Constantin, you may want to register your module with the newly-created Third Party Modules Registry (for lack of a better name), until the time of the official inclusion comes. You can find it at http://wiki.squid-cache.org/ThirdPartyModules Thanks, welcome, and good work! I have just registered the module as suggested: http://wiki.squid-cache.org/ThirdPartyModules/EcapGzip -Constantin
Re: Introduction and new eCAP GZIP adapter
On Mon, 2009-01-05 at 19:12 +0100, Constantin Rack wrote: As a welcome gift, I have released a new open-source eCAP adapter for HTTP compression: http://www.vigos.com/products/eCAP/ I would like to maintain and further develop this adapter, hoping that it will be included in the official SQUID distribution some day. Hello Constantin, Nice gift, thank you. Your adapter changes response content and content type. Should it be more careful about the E-Tag header? Will it work with 206 partial responses containing a single range (see the Content-Range header)? Should the adapter honor the no-transform cache-control directive by default? Should it add Warning 214 (Transformation applied)? These are RFC 2616 MUSTs, IIRC. Cheers, Alex.
Re: When can we make Squid using multi-CPU?
On Sun, 2009-01-04 at 10:03 +0800, ShuXin Zheng wrote: Hi, Squid current can only use one CPU, but multi-CPU hardware machines are so popular. These are so greatly wastely. How can we use the multi-CPU? Can we separate some parallel sections which are CPU wasting to run on different CPU? OMP(http://openmp.org/wp/) gives us some thinking about using multi-CPU, so can we use these technology in Squid? SMP support has been earmarked for Squid v3.2 but there is currently not enough resources to make it happen (AFAICT) so it may have to wait until v3.3 or later. FWIW, I think that multi-core scalability in many environments would not require another Squid rewrite, especially if initial support does not have to do better than running multiple Squids. You can monitor this project progress at http://wiki.squid-cache.org/Features/SmpScale Thank you, Alex.
Re: When can we make Squid using multi-CPU?
2009/1/8 Alex Rousskov rouss...@measurement-factory.com: SMP support has been earmarked for Squid v3.2 but there is currently not enough resources to make it happen (AFAICT) so it may have to wait until v3.3 or later. FWIW, I think that multi-core scalability in many environments would not require another Squid rewrite, especially if initial support does not have to do better than running multiple Squids. Well, people are already doing that where its suitable. Whats really missing for those sorts of setups is a simple(!) storage-only backend and some smarts in Squid to be able to push and pull stuff out of a shared storage backend, rather than relaying through it. The trouble, as I've found here, is if you're trying to aggregate a bunch of forward proxy squid instances on one box through one backend squid instance - all of a sudden you end up with lots of RAM wastage and things die at high loads with all the duplicate data floating around in socket buffers. :/ Adrian
