Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

I'd like to add a real-world use case to this thread. We want to use fetch aborting to rate limit our applications, in order to more evenly distribute our traffic to our upstream cloud providers. Currently this would be done inside the application code, by buffering and throttling the creation of outgoing requests. 

However, our users do often run multiple application instances (same domain) and we would prefer to be able to do the rate limiting via a single domain level Service Worker intercepting **all** of the requests, rather than having each application instance do it individually in a vacuum with no knowledge of the rates occurring in sibling application instances.

Items of interest to us:

- intercept the fetch before the request stream initiates (no traffic to upstream provider is critical)
- truly abort some requests, we only need the most recent request to go through in a given window of time


-- 
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/447#issuecomment-314228982