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.
---
Previous in thread (35 of 55): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (37 of 55): 🗣️ Philip Linde (linde.philip (a) gmail.com)