- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 26 Jun 2023 13:44:10 +1000
- To: Martin Thomson <mt@lowentropy.net>
- Cc: ietf-http-wg@w3.org
The original design took the approach you suggest, but that makes error handling awkward -- if an unsupported selector type is used, should that be skipped, or should the entire thing fail (in which case the cache needs to scan it first)?
Also, IME people batch purges by selector type, mostly. YMMV.
Cheers,
> On 26 Jun 2023, at 10:56 am, Martin Thomson <mt@lowentropy.net> wrote:
>
> On Sun, Jun 25, 2023, at 14:48, Mark Nottingham wrote:
>> - An HTTP Cache Invalidation API
>> <https://datatracker.ietf.org/doc/draft-nottingham-http-invalidation/>
>
> Is there any reason you can only use one type of selector in a request?
>
> {
> "type": "uri",
> "selectors": [
> "https://example.com/foo/bar",
> "https://example.com/foo/bar/baz"
> ]
> }
>
> Would this be better?
>
> {
> "uri": [
> "https://example.com/foo/bar",
> "https://example.com/foo/bar/baz"
> ],
> "uri-prefix": [
> "https://example.com/bar",
> ],
> }
>
--
Mark Nottingham https://www.mnot.net/
Received on Monday, 26 June 2023 03:44:20 UTC