Pipelining in Safari (Calling All Programers)

Posted:
in Mac Software edited January 2014
Though Safari is fast, it is not as fast as Chimera with Pipelining enabled. We have the source to Safari (webcore): <a href="http://developer.apple.com/darwin/projects/webcore/"; target="_blank">http://developer.apple.com/darwin/projects/webcore/</a>;



so is it possible to add pipelining?

I did a search on khtml and konqueror and I do not believe it has pipelining (though it can pipeline POP3 e-mail requests). So is there a way (calling all programmers) to add pipelining for html. I would be very curious to see how fast Safari could be with pipelining.

Comments

  • Reply 1 of 5
    jlljll Posts: 2,709member
    [quote]Originally posted by jdbon:

    <strong>Though Safari is fast, it is not as fast as Chimera with Pipelining enabled. We have the source to Safari (webcore): <a href="http://developer.apple.com/darwin/projects/webcore/"; target="_blank">http://developer.apple.com/darwin/projects/webcore/</a></strong><hr></blockquote>;



    That's the source to the rendering engine - not Safari.
  • Reply 2 of 5
    akacakac Posts: 510member
    I believe its been shown that pipelining is a *bad* thing because it can kill webservers needlessly. Safari uses the correct approach - and so does Chimera. Chimera does NOT have pipelining on by default and only through a pref does it allow it.



    But even there, the Chimera developers say its not necessarily a good thing.
  • Reply 3 of 5
    baumanbauman Posts: 1,248member
    I've heard a lot about pipelining recently... What is it and how does it work?
  • Reply 4 of 5
    cosmocosmo Posts: 662member
    [quote]Originally posted by bauman:

    <strong>I've heard a lot about pipelining recently... What is it and how does it work?</strong><hr></blockquote>



    pipelining basically sends multiple requests to the webserver instead of sending requests one at a time.

    This speeds things up when servers limit the speeds of each request/download and if you have a fast connection.
  • Reply 5 of 5
    chuckerchucker Posts: 5,089member
    [quote]Originally posted by Akac:

    <strong>I believe its been shown that pipelining is a *bad* thing because it can kill webservers needlessly.</strong><hr></blockquote>



    Not if the web servers behave properly. Pipelining is a defined feature of HTTP 1.1, which is already a few years old. Just because some web server products from *cough* M$ *cough* and others can't handle pipelining right doesn't mean it's a bad idea in general.



    By adding Pipelining to more browsers (at least as an option), some companies hopefully will realize they should switch to Apache.
Sign In or Register to comment.