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

[Ali Fardan]

On Sun, 8 Nov 2020 16:21:03 +0000
James Tomasino <tomasino at lavabit.com> wrote:
> Again, I'm not sure if caching is involved in it or not, but that's
> the best thing I could come up with as an answer to your question.

This can be done by remembering the offset percentage-wise in the
client for each previous page, however, this could be broken if caching
wasn't involved in case document changes meanwhile, if this is a
compelling reason to have caching, I'd suggest Mallick's method, as it
won't involve any changes to the protocol and it fits the context very
well.