Will it be smart and queue later requests for submission after earlier requests complete, or will it do something stupid like discard later requests which push it over its maximum number.
Is the answer the same across browsers, or does it vary?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Are you referring to the fact that browsers typically limit the number of simultaneous connections to a particular host (2 is recommended by the HTTP spec)? If so, then yes, all requests will be queued. It’s really no different then loading a web page that has a lot of images in it — the initial load will result in a bunch of new requests, but they may have to wait based on the connection limit. But all of your images do load.
I’m not aware of an ajax-specific request limit.