SillyDog701 Message Centre

[Don_HH2K]

As I've said here before, I've had a few problems loading images in the past, around the time I installed Windows XP Service Pack 2. This was also the time that I enabled a feature called "Pipelining" in Netscape.

Lately this image problem has been getting worse and worse, and sine everything worked fine in IE, I decided to have a look in my preferences to see what was going wrong.

To my surprise, disabling the "Pipelining" feature worked great. I'm able to view images and make large downloads.

As well as having this help other people experiencing the same problem, I would like to as this: why is it that this "Pipelining" feature, which is designed to improve page-load performance, has so many problems with images, etc...?

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

---

Laptop: Turion 64 X2 @ 2GHz, 2GB PC5300, 100GB HD, Radeon X300, 15" LCD, Vista Ultimate x64
Web server: P2 @ 233MHz, 280MB PC66, 20GB HD, 13.3" LCD, Windows Server 2003 x86
Misc. server: MIPS32 @ 216MHz, 16MB PC100, 4MB flash, DD-WRT Linux mipsel

[Fulvio]

It is not so straightforward. As far as I known Pipelining is not available in 7.1. You need the Prefbar. And, they say: Default Status: Hidden
Enables or disables http pipelining. This is supposed to speed up page loads over dialup, but not all servers support it.
For a a boring treatise I have one from w3c.org, this one will do.
http://www.mozilla.org/projects/netlib/http/pipelining-faq.html

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803

---

"I've got a very poor sense of direction. I keep forgetting which way is forwards."
WinXP, SP2, FF2.0.0.16, FF3.0.1, TB2.0.0.16, IE7.0, Opera9.51, SM1.1.11, Safari3.1.2, Sygate5.6; AVG8.01, JRE1.6_05

[Don_HH2K]

It appears to be available in "HTTP networking" under Advanced.
I'll provide a screenshot later if requested.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

---

Laptop: Turion 64 X2 @ 2GHz, 2GB PC5300, 100GB HD, Radeon X300, 15" LCD, Vista Ultimate x64
Web server: P2 @ 233MHz, 280MB PC66, 20GB HD, 13.3" LCD, Windows Server 2003 x86
Misc. server: MIPS32 @ 216MHz, 16MB PC100, 4MB flash, DD-WRT Linux mipsel

[Fulvio]

[profman]

Here are some old theads on "pipelining."

Mozilla Pipelining
speeding up netscape

I imagined at one time that enabling this option did speed up matters up a bit (I was on broadband type connections), but I currently am not sure that the difference was real.

I am pretty sure that either the "Enable Pipelining" option or the "Enable Keep-alive" option was causing my browser to hang at my office when trying to load certain sites. (Disabling "Keep-alive" also seems to disable pipeling). In any case, disabling these options at work almost certainly stopped the hanging behavior. My office system is on a LAN behind a firewall proxy-server and I suspect that this caused the problems with these settings. My home systems never seemed to have any problems with these settings.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616

---

profman, the mad chemist
Moderator of SillyDog Forums
User of Thunderbird 2.0.0.x & Firefox 2.0.0.x
Try Forum Search or Visit NETSCAPE (+ more) SOLUTIONS