Latest software headlines from Network World:
Kernel developers, Wall Street to come together
Zoho launches e-mail app with offline, mobile access
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
Author's reply to "Only two simultaneous HTTP connections?" post
I'm the editor who worked the Thomas Powell on this article and I am posting his response here.
"Much of the conventional wisdom about Ajax is simply wrong.
Take a look at this demo, I outline in my book about Ajax: http://ajaxref.com/ch6/requestqueue.html
It shows the following:
Ten requests are spawned all asynchronously. The first will have a five second delay, the second will have a seven second delay and the rest will have no latency.
In this example, I have the library timeout around 5 seconds, and thus, given a two connection limit with the two slow pokes in the front, everyone timeouts. If you click on request queue, which will order the requests, you will see that just the first two timeout and then everybody else goes through.
That looks like a limit to me. -- TAP"