> > I would like comments on the suggestion contained at this website:
> >
[quoted text clipped - 19 lines]
>
> Essentially, this is an experimental option.
I made these changes in WaMCom 1.3.1 on my G4 running OS 9.2.2. I
haven't tested to see if this has improved performance, but I haven't
noticed any unwanted results, either.
Happy browsing,
Eric
Warren Oates - 18 Oct 2006 23:32 GMT
In article
<ericp06-DDCBE2.14593918102006@newsclstr02.news.prodigy.com>,
> I made these changes in WaMCom 1.3.1 on my G4 running OS 9.2.2. I
> haven't tested to see if this has improved performance, but I haven't
> noticed any unwanted results, either.
I've made those changes before, and the difference even on the old G4
seemed negligible. On my Mac Pro, it didn't seem to make any difference
at all, except that I couldn't access my router, so I changed it back. I
have the DNS proxy thing set, to use with Tor, though.

Signature
W. Oates
Teal'c: He is concealing something.
O'Neil: Like what?
Teal'c: I am unsure, he is concealing it.
Clever Monkey - 19 Oct 2006 20:11 GMT
> In article
> <ericp06-DDCBE2.14593918102006@newsclstr02.news.prodigy.com>,
[quoted text clipped - 7 lines]
> at all, except that I couldn't access my router, so I changed it back. I
> have the DNS proxy thing set, to use with Tor, though.
Those multiple connections make some turn-key routers very confused.
Lots of talk about this on various tech forums.
Clever Monkey - 19 Oct 2006 20:18 GMT
>>> I would like comments on the suggestion contained at this website:
>>>
[quoted text clipped - 23 lines]
> haven't tested to see if this has improved performance, but I haven't
> noticed any unwanted results, either.
Of course, getting the results you expected (no harm done to your
connectivity) is no proof that this experimental setting is ready for
prime-time.
The main issue is not that one can enable this and instantly know if it
fails or not. The problem is that one can enable it and then forget
about it until some weird networking issue comes up that takes days to
solve. One you get down to "this browser works, this one does not" you
are half-way there. One still has to remember they made the change.
The assumption is that the person who made the change is also the person
trying to use the browser in question. This is why the option is hidden.
That being said, I've been running with HTTP pipelining for as long as
Mozilla has supported it. Besides one problem with an HTTP/1.0 server
that said it was HTTP/1.1, I've had no problems, either.