Today, users can really only take advantage of HTTP caching by implementing their own client filters. It would be nice to have a built-in mechanism for caching HTTP responses for JAX-RS / MP Rest Client.
For a client implementation, it might be possible to implement a client response filter that handles 304s by looking up previously cached responses based on the eTag and/or URI. The feature would also need a mechanism to clear stale entries from the cache.
Today, users can really only take advantage of HTTP caching by implementing their own client filters. It would be nice to have a built-in mechanism for caching HTTP responses for JAX-RS / MP Rest Client.
Here is a great resource for understanding HTTP caching in JAX-RS: https://dennis-xlc.gitbooks.io/restful-java-with-jax-rs-2-0-2rd-edition/content/en/part1/chapter11/caching.html
For a client implementation, it might be possible to implement a client response filter that handles 304s by looking up previously cached responses based on the eTag and/or URI. The feature would also need a mechanism to clear stale entries from the cache.