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

[boringcactus]

On 2020-11-08 12:49 AM, Sean Conner wrote:
>    My approach is a bit different, probably a bit harder to implement server
> side, but deals not only with the caching issue, but with repeated requests.
> I'm not sure how popular it will be, but hey, it's out there, and it only
> adds one general purpose status code (23 for now) that means:
> 
> 	okay, request was okay, but there is no data to serve you.
You could get a similar effect with 44 SLOW DOWN as it already exists, 
and boom, now the protocol doesn't need to know about caching at all.