Re: [w3c/ServiceWorker] respondWith is not implementable as written (#1168)

I believe this is an issue with the ReadableStream integration into fetch and SW specs.  @yutakahirano and @jungkees might be able to help?

At least in gecko we are planning to do something like this:

1. If stream has a native inner source, then just consume that in native code directly.
2. If stream has a js inner source, then pump the ReadableStream into a buffer on the js thread, possibly applying back pressure if the buffer fills up.  The native code then reads from this buffer as one of its native streams.

I don't know if this helps develop safe spec language or not.  Not sure what blink does here.

-- 
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/1168#issuecomment-317031289