Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947)

So if we assume the cost for HTTP/2 approaches zero in the future, the main features WebSocket has that Fetch does not would be:

1. Smaller frames.
2. Dedicated connection.

It feels like we should explore exposing those "primitives" to Fetch somehow if they are important.

It worries me a little bit that @wenbozhu claims that HTTP is not full-duplex whereas the discussion in https://github.com/whatwg/fetch/issues/229 concluded it pretty clearly is. I hope that's just a misunderstanding.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/947#issuecomment-336478057

Received on Friday, 13 October 2017 15:00:57 UTC