[
https://issues.apache.org/jira/browse/HTTPASYNC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098016#comment-15098016
]
Oleg Kalnichevski commented on HTTPASYNC-100:
---------------------------------------------
You'll naturally need to get yourself acquainted with HTTP cache code and to
some extent with that of HttpAsyncClient. One way to start would be to review
the existing code for conformance with RFC 7234, which at this point HttpClient
is not compliant with. Later, one would need to redesign the existing APIs and
make it possible to use the cache in a non-blocking mode.
Oleg
> Provide caching for streamed HTTP exchanges in CachingHttpAsyncClient
> ----------------------------------------------------------------------
>
> Key: HTTPASYNC-100
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-100
> Project: HttpComponents HttpAsyncClient
> Issue Type: Improvement
> Affects Versions: Future
> Reporter: Brian Chang
>
> The current implementation of {{CachingHttpAsyncClient}} doesn't support
> caching of streaming exchanges. It would be very useful to have this
> functionality implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
