You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really shocked because I come from Turbolinks and found Unpoly by accident: WONDERFUL! CONGRATULATIONS!
Just one question (coming from Turbolinks): is there a way to load the cached page (just like it happens default way) but check in "background" in parallel for new content on that page and replace the content with new one if available?
... during standard navigation (via Application Visits), Turbolinks will immediately restore the page from cache and display it as a preview while simultaneously loading a fresh copy from the network. This gives the illusion of instantaneous page loads for frequently accessed locations.
The text was updated successfully, but these errors were encountered:
You can implement this with the JavaScript API, but it doesn't come out of the box.
This is something I would like to see Unpoly support with a convenient modifier like [up-cache=staged]. Any Implementation would need be need to more refined than Turbolinks', since an Unpoly update might only update a fragment, or open the content in a modal layer. Turbolinks 5 always swaps the entire page.
Right now the caching system kind of expects that only one user exists. Only clearing the cache after a non-GET request would always render outdated content if someone else made changes to records in the meantime. I think having an improved cache invalidation strategy would be vital.
I'm really shocked because I come from Turbolinks and found Unpoly by accident: WONDERFUL! CONGRATULATIONS!
Just one question (coming from Turbolinks): is there a way to load the cached page (just like it happens default way) but check in "background" in parallel for new content on that page and replace the content with new one if available?
From Turbolinks docs (https://github.com/turbolinks/turbolinks/#understanding-caching):
The text was updated successfully, but these errors were encountered: