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'd love to serve a fresh app from the edge initially but then serve it from the cache after that so that the app can be used while offline and so that the app can be more responsive when only a slow network connection is available.
I'd want to have the app automatically update asynchronously from the edge as well.
I think there'd need to be a way to mark routes as client cacheable. Some routes would only be available on the remote while others would be available locally too. There might be some use case for local cache only routes too but I'm thinking not because then you wouldn't be able to use that route until the local cache were populated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'd love to serve a fresh app from the edge initially but then serve it from the cache after that so that the app can be used while offline and so that the app can be more responsive when only a slow network connection is available.
I'd want to have the app automatically update asynchronously from the edge as well.
I think there'd need to be a way to mark routes as client cacheable. Some routes would only be available on the remote while others would be available locally too. There might be some use case for local cache only routes too but I'm thinking not because then you wouldn't be able to use that route until the local cache were populated.
Beta Was this translation helpful? Give feedback.
All reactions