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

@igrigorik We (Chrome) already have 30-sec timeout. It's implemented in multiple places for some reasons, but see [content::KeepAliveHandleFactory](https://cs.chromium.org/chromium/src/content/browser/frame_host/keep_alive_handle_factory.cc) for example. We also have a restriction on the number of requests in a way in [content::ResourceDispatcherHostImpl::HasSufficientResourcesForRequest](https://cs.chromium.org/chromium/src/content/browser/loader/resource_dispatcher_host_impl.cc?type=cs&q=ResourceDispatcherHostImpl::HasSufficientResourcesForRequest&l=1788).

As for the pending point in @sleevi's comment, it sounds that it is important regardless of keepalive flag.  Chrome already has some protection. I'm open to have such protection in the spec, and change Chrome's implementation if needed, but I don't think it's keepalive specific. Does this make sense?

-- 
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-360042699