Use case for cache as an interface

[timrobertson100]

Hi folks

I see the request for Cache to be an interface has been discussed before and closed since there is no real use case.

We make use of web service calls from an Apache Spark distributed processing environment and front it with a cache that's backed by HBase. As we're likely to tidy this area up in our own code, it would be nice if we could do an HBaseCache implementation to pass in. Before we go down the route of Interceptors, is there any interest in Cache becoming an interface, please?

Thank you

[yschimke]

Would passing in a different okio FileSystem work, or is that too granular? That is already supported.

okhttp/okhttp/src/jvmMain/kotlin/okhttp3/Cache.kt

Line 152 in f4ff4f4

constructor(

[timrobertson100]

Thank you very much @yschimke

This is more akin to an object store than an FS, so things like symlinks, creating directories, recursive listing etc wouldn't map over. Ideal to me would be a cache interface that had only the minimal init, get, put, delete (or so), with the implementor choosing how that was stored. Thank you for looking.

[yschimke]

You wouldn't need to implement those. I think this is our POR for different Cache storage.

See #2903 (comment)

As an example https://gist.github.com/mandrachek/5da100d508eebf57a94de81448dcadaa