Re: [whatwg/fetch] Add compression dictionary negotiation and decoding to the fetch processing model (Issue #1739)

Sorry, thinking through it more, it makes sense for fetch to include the steps for managing the dictionaries like it does with cache entries.

Still a lot of fleshing out to do (and I need to define the actual dictionary storage) but does plugging it in something like [this](https://github.com/whatwg/fetch/compare/main...pmeenan:fetch:dictionaries) make sense? That moves all of the dictionary processing into a separate layer between cache and network.

Does bypassing the middle step for clients that don't support dictionary compression make sense to include?

I can move it to a work-in-progress PR so I can iterate on it there if the general framework looks like a good way to plug it in.

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

Message ID: <whatwg/fetch/issues/1739/2327071308@github.com>