[
https://issues.apache.org/jira/browse/CXF-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131667#comment-14131667
]
Sergey Beryozkin commented on CXF-5996:
---------------------------------------
Hi Romain
Re the reader/writer enhancements, Writer/Reader Interceptor are more meant to
be 'simpler' MessageBodyWriters/Readers, and all the reader/writer interceptors
can do the filters can do. I reckon the most realistic enhancement is can be
"be able to give properties between filters and interceptors surely", because
if Response need to be returned then filters should be used and writer/reader
contexts offer getHeaders() method...
ClientRequestFilterContext has abortWith(Response), i.e, the request filter
would do something like
"context.abortWith(Response.ok(getEntityFromjCache()).build())".
So we'd have a Response with the entity extracted from the local cache coming
into the client response processing chain. So the next thing we'd do is we'd
have a reader interceptor blocking the read because Response already has an
entity.
May be I miss something, but it should work ?
Cheers, Sergey
> respect client cache headers
> ----------------------------
>
> Key: CXF-5996
> URL: https://issues.apache.org/jira/browse/CXF-5996
> Project: CXF
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
> Attachments: client-jaxrs-cache-control.zip
>
>
> Hi
> would be great to get a mecanism (maybe using jcache as abstraction) to
> respect on client side http cache headers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
