5 ms·
Have they fixed the ridiculous "Only one connection allowed at a time to an http server" change yet? :/ As far as I'm aware, the browser is fairly unusable beca
by mibbitier 14y ago
Have they fixed the ridiculous "Only one connection allowed at a time to an http server" change yet? :/
As far as I'm aware, the browser is fairly unusable because of this.
- ghostganz 14y agoI found the browser a lot better/faster on my 3GS after the update, probably due to Javascript speed improvements, so it's very far from "unusable".
- betterth 14y agoI haven't noticed anything and I use Safari/Chrome pretty heavily on my Touch. Under what conditions would this noticeably affect my browsing?
- kzahel 14y agoMobile safari should use SPDY, then this wouldn't be as much of a problem :-)
- pilif 14y agoThis limitation doesn't exist. Safari happily opens up to 4 connections per server. There is however a bug with long-polling connections: If you fire off the XHR for the long-polling endpoint (or Server Site Events endpoint for that matter) before window.onload has fired, then Safari will not fire onload (nor load any other external resource) until the long-polling connection closes or returns something. What you are seeing is people not updating their scripts yet to take this bug into account.
- lazugod 14y ago> What you are seeing is people not updating their scripts yet to take this bug into account. Why? Shouldn't the expectation be that the bug gets fixed?
- pygy_ 14y agoBecause meanwhile, your users/customers experience the bug, which for you means lost page views, mindshare and probably revenue...
- deleted 14y ago[deleted]