Hi, hoping to get some feedback on what people thought about the idea of an application-level layer to manage network requests. Hacked together this over a week or so; definitely not production ready. Thanks for checking it out.

I think it's an often ignored aspect of client side development. We often leave requests loading when we're not listening for their completion, stack too many requests, have many requests for the same thing, etc. I really like the facebook/dataloader approach for keeping a local identity map and batching requests but priority is still a concern.

It looks interesting to me, although I don't think I'm the one to judge how it would impact performance.

I'm curious what you were doing at the time that inspired you to build this or what particular problem you were solving then?

I was working on a web app where many requests were being made in many different code paths. There were noticeable slowdowns in UI pieces that were streaming data when a lot of network activity was occurring.

The video was trying to do two things at once: explain the goals and high level ideas as well as demonstrate "syntax" (the clicks and drag and drops). Since these are both new to people coming to your site, it's hard to digest at the same time. I'd love a video of just explaining what the demo is doing, since I didn't really understand how to program in the new approach you described.

The exact method is not that important but the goal itself. But of course, you have a point. The explanation is planned but had no time for it yet.