Sudipto Mallick <smallick.dev at gmail.com> writes: > The clients with history support and supports going ''backwards'' and > ''forwards'' through history should cache text/* responses in memory > for that browsing session. When the user browses through the history > using ''forward'' and ''backward'' action, no reloading should happen. > But, when a user clicks the link for a resource already in cache or > writes the link by hand or selects the link from previously visited > links or asks for reload: the cache is purged and the resource > reloaded. It is assumed that requests with query part are idempotent. I also believe that this is the correct approach, and should be considered a client 'best practice'. -- +-----------------------------------------------------------+ | Jason F. McBrayer jmcbray at carcosa.net | | A flower falls, even though we love it; and a weed grows, | | even though we do not love it. -- Dogen |
---
Previous in thread (50 of 55): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)
Next in thread (52 of 55): 🗣️ John Cowan (cowan (a) ccil.org)