Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Not quite...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Not quite...
Authored by: mholve on Jan 24, '03 10:48:33AM
While that explanation kind of makes sense... What is missing is the fact that the client/server have to initiate multiple connections for each piece of a page without pipelining. With it, is like having a persistent database connection - it's there, and it's wide open for data. With all the extra connections, you have more overhead. I would say that pipelining is still faster - perhaps not perceptually as the author indicates.

Just my take on it... Anyone seen any real benchmarks or know more about it?

[ Reply to This | # ]