Re: [PATCH] replace RFC2181 magic numbers with POSIX definitions
Bundle Buggy has detected this merge request. For details, see: http://bundlebuggy.aaronbentley.com/project/squid/request/%3C4B078096.40803%40treenet.co.nz%3E Project: Squid
Re: Squid-3 and HTTP/1.1
FWIW, I have an XSLT stylesheet that can format the results pleasantly; it could be a starting point for something automated. On 29/01/2010, at 12:34 AM, Amos Jeffries wrote: > Robert Collins wrote: >> On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote: >>> c) Co-Advisor currently only tests MUST-level requirements. Old Robert's >>> checklist contained some SHOULD-level requirements as well. I see that >>> Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and >>> Sheet1) for now, until all MUSTs on Sheet2 are satisfied? >>> >>> d) I do not know who created the spreadsheet. Whoever it was, thank you! >>> Is there a script that takes Co-Advisor results and produces a >>> spreadsheet column for cut-and-pasting? >> It looks nice. It might be based on the xls spreadsheet I made, but I >> don't know ;) >> I would not worry about SHOULD's until the MUSTs are done (but if a >> SHOULD is in reach while doing a MUST, doing it would be good). >> -Rob > > Spreadsheet by me. Item format + naming by the Co-Advisor authors. Data by Y! > testing + me for the estimated column. > > I tried to base it on yours Rob for a historical view of the 2.x support. But > the item naming and crossover was too different and too much work to be > reliable and easy. half-sorry ;) > > Alex: the current form is effectively a XLS dump cross-test of the Co-Advisor > results. Plus manual estimations for the "guess" column. > > I've forgotten what was on the Sheet2. So yes it's missed a few rounds of > updates. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21 > Current Beta Squid 3.1.0.15 -- Mark Nottingham m...@yahoo-inc.com
Re: [PATCH] log virgin HTTP request headers
On 01/28/2010 06:07 AM, Robert Collins wrote: > Just a small thing: can I suggest s/virgin/pristine/ ? Or > s/virgin/received/ ? Pristine may work, but we (and other adaptation related documents) use virgin in many places already, including APIs. Received is a bad idea because an adapted message is also received. > virgin has a sexual connotation in some cultures, and can be confusing > in a way that is avoidable. Tell that to the Virgin Islands folks. :-) Cheers, Alex.
Re: [PATCH] log virgin HTTP request headers
> Just a small thing: can I suggest s/virgin/pristine/ ? Or > s/virgin/received/ ? > > virgin has a sexual connotation in some cultures, and can be confusing > in a way that is avoidable. The "virgin" is a term which used extensively in squid3 specially in adaptation code. But id required I can make this change... Christos > > -Rob >
Re: Squid-3 and HTTP/1.1
Robert Collins wrote: On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote: c) Co-Advisor currently only tests MUST-level requirements. Old Robert's checklist contained some SHOULD-level requirements as well. I see that Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and Sheet1) for now, until all MUSTs on Sheet2 are satisfied? d) I do not know who created the spreadsheet. Whoever it was, thank you! Is there a script that takes Co-Advisor results and produces a spreadsheet column for cut-and-pasting? It looks nice. It might be based on the xls spreadsheet I made, but I don't know ;) I would not worry about SHOULD's until the MUSTs are done (but if a SHOULD is in reach while doing a MUST, doing it would be good). -Rob Spreadsheet by me. Item format + naming by the Co-Advisor authors. Data by Y! testing + me for the estimated column. I tried to base it on yours Rob for a historical view of the 2.x support. But the item naming and crossover was too different and too much work to be reliable and easy. half-sorry ;) Alex: the current form is effectively a XLS dump cross-test of the Co-Advisor results. Plus manual estimations for the "guess" column. I've forgotten what was on the Sheet2. So yes it's missed a few rounds of updates. Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21 Current Beta Squid 3.1.0.15
Stress testing.
I have today managed to negotiate some hands-on time with a box that runs Debian vanilla kernel and can pump 9.8G bytes/sec of traffic. It runs on 2x Xeon cores with 36GB RAM. No disk worth mentioning. All we need is to: - provide .deb builds of Squid for install (done). - have something to generate the load (server and client) - get testing done before the box needs to be put into production "sometime". I thought web polygraph. Provided I can also negotiate access to a cluster of load machines to run the load. And figure out the test setup/config. Help? Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21 Current Beta Squid 3.1.0.15
Re: [PATCH] log virgin HTTP request headers
Just a small thing: can I suggest s/virgin/pristine/ ? Or s/virgin/received/ ? virgin has a sexual connotation in some cultures, and can be confusing in a way that is avoidable. -Rob signature.asc Description: This is a digitally signed message part
Re: Squid-3 and HTTP/1.1
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote: > c) Co-Advisor currently only tests MUST-level requirements. Old Robert's > checklist contained some SHOULD-level requirements as well. I see that > Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and > Sheet1) for now, until all MUSTs on Sheet2 are satisfied? > > d) I do not know who created the spreadsheet. Whoever it was, thank you! > Is there a script that takes Co-Advisor results and produces a > spreadsheet column for cut-and-pasting? It looks nice. It might be based on the xls spreadsheet I made, but I don't know ;) I would not worry about SHOULD's until the MUSTs are done (but if a SHOULD is in reach while doing a MUST, doing it would be good). -Rob signature.asc Description: This is a digitally signed message part
