Re: [w3c/ServiceWorker] Tee-ing Cache.put()? (#1367)

Yes, with sufficient work on the HTTP+DOM caches, I think most (all?) of the optimizations I was imagining for `teePut` could be achieved for the common `clone()` patterns, so that's a fair point.  `teePut` seems nice in being simpler to write for a common case while encouraging a fast path that could be achieved more readily in browsers today, but I don't know whether that makes it worth it as a new feature.

-- 
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/1367#issuecomment-445477005