[Webkit-unassigned] [Bug 32945] Only 4 simultaneous connections with xmlhttprequest

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Dec 27 03:07:21 PST 2009


https://bugs.webkit.org/show_bug.cgi?id=32945


Jurek Raben <jurekraben at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jurekraben at gmail.com




--- Comment #2 from Jurek Raben <jurekraben at gmail.com>  2009-12-27 03:07:18 PST ---
I find this quite interesting. In my opinion Websites will have more and more
simultaneous Ajax connections. My cms loads all content areas with Ajax Calls.
I can Change it to maximal 4 parallel calls and the following to Serial. The
only Problem is that if you have Interactive Elements Like Flash  in the page
also, it can result in à total loading Block As it was in my Case.

I Managed to fix this by moving Streaming contents to another cname/subdomain. 

I think what happened on my page is this:

- mp3 was streaming and taking 1 Download slot
- 4 xmlhttprequests were started and Never finished before the mp3 Download
completed. 3 calls started, the fourth was blocked by Safari.

Now this seems to me somehow buggy. The 3 xml requests finished loading,so in
fact there were now 3 free download slots again. Why Safari didn't start then
with the fourth xml request? 

It seems to me that Safari doesn't recognise freed xml slots within a loading
xml Slot.

One First "workaround" was to Start all xml requests with a timeout by using
setTimeout(Connection.send(),Connection_Num x 150)

this fixed the Problem only sometimes, but it changed the loading behaviour of
Safari. maybe because Safari only Checks free slots for xml requests at the
beginning of the Request?

I didn't find any useful Information about These Limits. So i think it Needs to
Be better documented.

Best regards

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list