Do we have some config to cache the downloaded fragments in JS memory?

[JackPu]

Is your feature request related to a problem? Please describe.

Background
Our app is running on some OTT platforms. But there is a lot of limited policy on those platforms especial for browser cache. I mean, if we re-download some fragments from some position, we still get new ones from the HTTP request.

So my question is: Can we provide some config option to control how long of the fragments we can keep in our memory cache? And if we match the cache, we reuse them, not send the new request?

Describe the solution you'd like

I may cache it in our fragment-loader by a number config.

Additional context

No response

[robwalch]

There are plans to preload segments and cache the results until loaded:

• Feature: Implement support for LL-HLS #EXT-X-PRELOAD-HINT part loading #6356

While that does not include caching segments loaded normally or configuring what and how much segment data to cache, these are relative concerns. Init segments would be a good place to start. Automatic removal of cached segment and playlist data should also be considered.