On Fri, May 12, 2017 at 8:49 PM, Frank Bonetti <[email protected]> wrote:
> To give you some context, I'm working on a single page app: > > 1. When the user loads a particular page, the app makes 10 independent > ajax requests to get various pieces of data. Some of these requests take a > while to complete while others complete instantaneously. > 2. In general, it doesn't matter when these requests start and end, but > there is one particular request which needs to be executed as quickly as > possible in order to make the page feel snappy. > 3. Since the browser can only execute a* limited number of ajax requests > in parallel, the order of when the requests start is critical.* If my > most important request is put last in the queue, it won't be executed until > the AJAX thread pool frees up a spot, which could take a while, resulting > in a page that feels slow. > This is important information. I don't know what the solution could be but this sounds like a scenario to be aware of. Maybe make an issue on the core where to describe the interaction between Cmd.batch and the limit of requests a browser can make concurrently. This SO answer might have relevant info <http://stackoverflow.com/a/561068/626515> . -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
