This is specifically about GWT’s RequestBuilder, but should apply to general XHR as well. My company is having me build a near realtime chat application over HTTP. Yes, I do realize there are better ways to do chat aplications, but this is what they want. Eventually we want it working on the iPad/iPhone as well so flash is out, which rules out websockets and comet as well, I think?
Anyway, I’m running into issues were I’ve set GWT’s RequestBuilder timeout to 10 seconds and we get very random and sporadic timeouts. We’ve got error handling and emailing on the server side and never get any errors, which suggests the underlying XHR request that RequestBuilder is built on, never gets to the server and times out after 10 seconds.
We’re using these request to poll the server for new messages rather often and also for sending new messages to the server and also polling (less frequently) for other parts of application. What I’m afraid of is that we’re running into the browsers limit on concurrent connections to the same domain (2 for IE by default?).
Now my question is – If I construct a RequestBuilder and call it’s send() method and the browser blocks it from sending until one of the 2 connections per domain is free, does the timeout still start while the request is being blocked or will it not start until the browser actually releases the underlying XHR?
I hope that’s clear, if not please let me know and I’ll try to explain more.
Browsers allowed only 2 connections per hostname; that has now changed. ‘Modern’ browsers allow upto 6 simultaneous connections – it varies between browsers. See http://www.browserscope.org/ – network tab.
As regards the timer, it starts before GWT invokes
xhr.send(), so your suspicion is right. See Request.java and RequestBuilder.java if you want to trace it out.