Studying this, I found that according to this issue and this page , browsers automatically redirect HTTP requests to the same server somewhere between 6 and 13 simultaneous requests, and they queue additional requests until other requests are completed. Therefore, apparently, no action is required, and I can just let my code fly.
I looked at angular-http-throttler (suggested by nathancahill), but (1) it duplicates what browsers already do themselves, and (2) it does not (currently) have an error management mechanism, so if the server does not respond, or if it was a bad request, it does not reduce the number of requests, so the queue is clogged up forever.
Giving the browser queue too many requests at the same time can cause memory / performance problems when working with very large amounts of data. I looked at various methods for creating a fixed-length queue in javascript, where it can turn off the callback when the queue location becomes available, but the non-blocking nature of javascript makes such a queue complex and fragile ... I hope you wonβt have to go into this direction (I don't mean a lot of data), and browser throttling will suffice for me.
Troy
source share