Re: [squid-users] squid 2.7 vs 3.x

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Well.

I've had squid-3 in production doing ssl reverse-proxy custom stuff
since 2 years ago. Shame on me, for believing the squid developers when
they said, expect a squid-3 release rsn.

On the c++ front, I submitted code trivially using STL <list> and was
informed, that's not allowed. Not allowed? Sorry, Squid-3 is not (or
was not) using c++.

I'm happy to see forward movement in any direction. However, I think
it's strongly in the interest of all Squid developers and users to get
together and structure a single road-map to a future that is really
delivered, with frequent incremental delivery of new code.

By the way Adrian, what does it mean to improve HTTP/1.1 compliance?
Does Squid 2.7 really support HTTP/1.1?

Matt

Adrian Chadd wrote:
| On Sat, Jan 12, 2008, Marcus Kool wrote:
~ integrated ICAP support; Amos has ipv6 support included in 3.HEAD.
|
| 2.x: functional cyclic filesystem (COSS), some of my recent work
| (store URL rewriting to allow CDN type content to be cached with
| appropriate administrator intervention; my logging helper framework
| to make logging lightweight again and allow other logging
destinations
| to be easily written, like UDP, MySQL, etc), performance
improvements,
| HTTP/1.1 compliance improvements.
|

- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHirZZJiSUUSaRdSURCMkpAJsGztPJdn06U/fmrAf73diHLClgbgCgj3mh
L1jIaUZr58CNB++wQ7yyDQ0=
=U0Ss
-----END PGP SIGNATURE-----
Received on Sun Jan 13 2008 - 18:11:08 MST