Re: [slightlyoff/ServiceWorker] Cache transactions & fixing `addAll` (#823)

I retract the deleteResponse suggestion.  I still think transactions combined with waitUntil support are super-powerful and may be used as a primitive for cool things that are unrelated to the intent of Cache, but transactions do seem like the best option for user code and implementer code.  (And waitUntil is the only sane way to allow a transaction to do data-dependent things while holding the transaction open since body reads are async and don't happen directly from the Cache API, making IDB self-closing transaction semantics infeasible or just jerky.)  Hooray for transactions!

---
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/823#issuecomment-206978460