Re: [whatwg/fetch] keepalive: Do we need to restrict the number of requests at a time? (#662)

Right, I think the non-enforcement was an oversight we should try to
correct. In the best/worst case, we would limit to 256 parallel requests -
but I’m not sure if we’d limit total pending.

I think the limit may vary on device, and thus be implementation defined
with advisory (SHOULD) guidance. At some point, these are consuming
resources that are not associated with a browsing context, and thus we need
overall limits and per-origin limits. Where do we think the upperbound of
resource usage is? 1024KB seems a rather substantial amount of information
to allow to be queued - but it depends on device and network, and allows
quick consumption by a single origin/navigation context.

On Mon, Jan 15, 2018 at 6:47 PM Anne van Kesteren <notifications@github.com>
wrote:

> To be clear, and as I tried to say in the thread, I'm fine with adding a
> limit. I was just raising the point that you might not have enforced one
> thus far. Is 64 requests reasonable? 16? Something that's not a power of 2?
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/whatwg/fetch/issues/662#issuecomment-357749703>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ABayJ3iEjLuTeUUmf5F-anugiaG_1qGIks5tK48XgaJpZM4ReaZf>
> .
>


-- 
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/662#issuecomment-357751499