Re: [whatwg/fetch] Double-keyed HTTP cache (#904)

@annevk I suspect we'd also need to update [connection pools](https://fetch.spec.whatwg.org/#concept-connection-pool) as well to extend that concept. Or were you thinking of doing it separately? I wasn't sure if https://github.com/whatwg/fetch/issues/904#issuecomment-491195621 extended to those changes as well?

I ask, because I'm wondering if it makes sense if, similar to how ["connection"](https://fetch.spec.whatwg.org/#concept-connection) is defined as an aggregate of both `origin` and `credentials`, it might make sense to define the concept as an aggregate function (which is made up of, for now, `first-party origin`, a singular value), which would then
1) Allow you to extend the definition if there are other attribute keys (e.g. TBB uses the TOR circuit ID as part of the key, IIRC)
2) Allow that concept to be reused between the "connection group" and "HTTP cache".

Incrementalism also works, I just wanted to make sure that was your goal.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/904#issuecomment-511897516