Caching and sizes, the explosion of responise codes (was Re: Caching and status codes)

[khuxkm at tilde.team]

November 8, 2020 12:18 AM, "Sean Conner" <sean at conman.org> wrote:

> I have my own ideas about caching, but I want to cobble up a
> proof-of-concept first before I talk about it more, because from where I
> come from, working code is worth more than talk.
> 
> -spc

Speaking of cobbling up proof-of-concepts, I've created a proof-of-concept of how I feel these cache-hint success codes would work:

https://gist.github.com/febd3f5ae2308e8b55449a92c6e58a65

(Yes, I know it's on GitHub, but I have a shell script to make Gists from the command line and so I want to use it.)

This includes a spartan client (it literally just spits the raw protocol response out at you) with caching behavior influenced by 21/22 (in practice, it caches all 2x responses except for 22 responses), as well as examples of endpoints to hit that return each code.

Hopefully my working code will prove my point better than I could in words.

Just my two cents,
Robert "khuxkm" Miles