The iPhone doesn't start queuing NSURConnection s. That's totally your responsibility. The iPhone will start all your asynchronous NSURLConnection s in parallel.
The only thing that will stop it is your memory :) I recently implemented a connection pool (my solution was based on NSOperationQueue ) just because of that. Now I can control parallel connections and my app doesn't crash when loading hundreds of avatar images.
So the reason I assumed there may be a simultaneous connection limit at the mobile OS level is because many mobile browsers enforce one. There are techniques for speeding up loading speed of the mobile version of your website by ensuring that there are as few additional content fetches as possible. Images are the main culprit, but css files, javascript files, etc all require an additional connection.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.