Your message dated Mon, 28 Dec 2009 17:41:56 +0100
with message-id <[email protected]>
and subject line Re: Bug#284621: mozilla-firefox: enable http pipelining?
has caused the Debian Bug report #284621,
regarding mozilla-firefox: enable http pipelining?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
284621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284621
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mozilla-firefox
Version: 1.0-4
Severity: wishlist


Here (http://computercops.biz/postt79998.html) it says that enabling
http pipelining is a speedup. I haven't measured it, but if it does no
harm (compatible with older web servers?), it could be a good thing.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-386
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages mozilla-firefox depends on:
ii  debianutils               2.10.4         Miscellaneous utilities specific t
ii  fontconfig                2.2.3-4        generic font configuration library
ii  libatk1.0-0               1.8.0-3        The ATK accessibility toolkit
ii  libc6                     2.3.2.ds1-19   GNU C Library: Shared libraries an
ii  libfontconfig1            2.2.3-4        generic font configuration library
ii  libfreetype6              2.1.7-2.3      FreeType 2 font engine, shared lib
ii  libgcc1                   1:3.4.3-4      GCC support library
ii  libglib2.0-0              2.4.8-1        The GLib library of C routines
ii  libgtk2.0-0               2.4.13-1       The GTK+ graphical user interface 
ii  libidl0                   0.8.3-1        library for parsing CORBA IDL file
ii  libjpeg62                 6b-9           The Independent JPEG Group's JPEG 
ii  libkrb53                  1.3.5-1        MIT Kerberos runtime libraries
ii  libpango1.0-0             1.6.0-3        Layout and rendering of internatio
ii  libpng12-0                1.2.8rel-1     PNG library - runtime
ii  libstdc++5                1:3.3.5-3      The GNU Standard C++ Library v3
ii  libx11-6                  4.3.0.dfsg.1-8 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-8 X Window System miscellaneous exte
ii  libxft2                   2.1.2-6        FreeType-based font drawing librar
ii  libxp6                    4.3.0.dfsg.1-8 X Window System printing extension
ii  libxrender1               0.8.3-7        X Rendering Extension client libra
ii  libxt6                    4.3.0.dfsg.1-8 X Toolkit Intrinsics
ii  psmisc                    21.5-1         Utilities that use the proc filesy
ii  xlibs                     4.3.0.dfsg.1-8 X Window System client libraries m
ii  zlib1g                    1:1.2.2-3      compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-1

On Thu, Dec 09, 2004 at 11:13:45PM -0500, Eric Dorland wrote:
> * Pablo Barbachano ([email protected]) wrote:
> > Package: mozilla-firefox
> > Version: 1.0-4
> > Severity: wishlist
> > 
> > 
> > Here (http://computercops.biz/postt79998.html) it says that enabling
> > http pipelining is a speedup. I haven't measured it, but if it does no
> > harm (compatible with older web servers?), it could be a good thing.
> 
> Shit, if Captain said it, it must be true right? :)
> 
> Seriously, I'm not sure about it. It would potentially screwup on
> admitidly broken webservers, but still that's not good. And the
> performance benefits don't really seem there... might help modem users
> but hurt people with faster connections. I dunno, give it a try and
> let me know how it goes in a week or two.

I'd say this is not a problem at all anymore, as the number of
concurrent requests sent to a server has been raised, instead.
(network.http.max-connections*)

Mike


--- End Message ---

Reply via email to