Caching timeline, toots and media #14

Open
opened 2024-09-25 07:00:44 +00:00 by Rubicon · 3 comments
Owner

This is a discussion about caching toots and media. It’s needed feature because caching significantly reduces the "empty" time as the app started.

This is a discussion about caching toots and media. It’s needed feature because caching significantly reduces the "empty" time as the app started.
Rubicon added the
feature
proposal
label 2024-09-25 07:00:44 +00:00
Author
Owner

What’s more, We already have a very simple toot cache for hero animation. The new cache system can ease the burden to set the cache.

What’s more, We already have a very simple toot cache for hero animation. The new cache system can ease the burden to set the cache.
Author
Owner

I think we may need separated:

  • timeline cache
  • toot cache and media cache

The toot and media cache can be done with the Web Cache API, as they can be seen as atomic data. The timeline cache is composed data so we may need indexed db to implement it correctly.

Additionally, the timeline cache may need to able to have hole - if we don’t actually fetch the whole missing part of the timeline.

Compatibility:

  • IndexedDB 2.0: all targets support
  • Web Cache API: all targets support
I think we may need separated: - timeline cache - toot cache and media cache The toot and media cache can be done with the Web Cache API, as they can be seen as atomic data. The timeline cache is composed data so we may need indexed db to implement it correctly. Additionally, the timeline cache may need to able to have hole - if we don’t actually fetch the whole missing part of the timeline. Compatibility: - IndexedDB 2.0: all targets support - Web Cache API: all targets support
Author
Owner

a RPC server is added into the service worker - we can use it to communicate with the service worker.

a RPC server is added into the service worker - we can use it to communicate with the service worker.
Sign in to join this conversation.
No description provided.