Interesting read, thank you.
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]
|
|
anony
Well done, folks. I am enlightened.
Only two simultaneous HTTP connections?
"Ajax applications are limited by HTTP to two simultaneous connections to the same URL. This is the way the HTTP protocol is designed, not some browser bug or limitation."
Nope. HTTP has no such limitations.
Correct, there is no
Correct, there is no limitation, in that you can modify your browser to make more than 2. However based on standards (and being a good web citizen) you really shouldn't.
It's like saying that a car is limited to under 5 feet wide (I have no idea how wide a car is so if that's off, sorry). Sure, you *could* build a car that was 50 feet wide...but that doesn't mean best practices and usability would allow you to do so.
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"
I don't remember there being
I don't remember there being such a limitation mentioned in either of the RFC's defining HTTP. Sounds like the web server in question was configured to allow only 2-3 simultaneous connections from one client.
It is in section 8.1.4 of
It is in section 8.1.4 of the HTTP/1.1 RFC 2616:
"A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy."
3 pages?
Why not put this on 1 page? Buried on Digg, but I'm sure you'll delete this comment.
Why put this on 1 page? It is easier to read and find your plac
Why put this on 1 page? It is easier to read and find your place when you do not have 10 screen lengths to scroll. I like that they put it on a few pages.
Ignore him...
...he's a digger and over there they think everything is a capitalist plot to push ads on them, even though they all use AdBlock anyway.
buried on digg?
Anon -- Get over yourself! It was good content and it wasn't over ten pages -- there was a reasonable amount of text per page.