[slightlyoff/ServiceWorker] should EventSource bypass service worker interception? (#885)

Currently we support intercepting EventSource.  I'm even adding a wpt test for this since its a way to observe a different FetchEvent.request.cache value.

While writing that test, though, it became apparent that EventSource is currently difficult to use with ServiceWorker.  EventSource is designed with the idea that the connection will be held open and lines will be flushed across the connection to trigger events.  This is quite difficult to do today with synthetic responses.  It might be possible in the future with streams, but you would still have to hold the SW alive.

@sicking suggested that we might want to treat EventSource like WebSocket and just bypass the service worker for now.

I feel like this is kind of a low priority item, but wanted to file the issue so we don't lose track of it.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/885