Re: [whatwg/fetch] consider exposing and allowing script to set Request priority (#436)

the priority low->high paradigm is certainly better than nothing.. at some point when combining different classes of things (or things from different sources - but that's outside the scope of one script) it devolves into  needing dependencies.. but that's a lot of complexity and a lot of complexity authors prefer to avoid and honestly screw up. As long as you're not combining things from multiple sources (i.e. things that aren't aware of each other or trust each other) you can mostly get by with priorities. Especially if you can reprioritize.

I'm not sure what the right balance in this API is but I lean towards at least some sense of classification if you don't feel full on deps are appropriate.

firefox does do a lot of dependency management for markup, but when it comes to scripts it has little idea what is going on.. and as mentioned before without some kind of classification or dependency system combining these scopes is super hard.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/436#issuecomment-267388838