On Sat, 2013-06-15 at 07:18 -0700, Sam Perman wrote: > I think it would be interesting to open those Apis up so the application > could get cache entries for use in certain error cases. (For example, my > client app has detected the server is unavailable for some reason or I have > crossed some throttling limit for requests to the backend... I could choose > not to attempt a call to the backend and just return the cache entry instead.) > > > ​sam >
I believe this should already be possible as long as your code can use the complete client stack, not just core. Though, to be sure ask Jon. He is the ultimate authority on everything related to HTTP caching. Oleg > On Sat, Jun 15, 2013 at 9:01 AM, Oleg Kalnichevski <ol...@apache.org> > wrote: > > > On Fri, 2013-06-14 at 14:23 -0700, Clover wrote: > >> Is there http/1.1 compliant(ish) caching classes like there are for the > >> http-client code? > > No, there are not. It should be possible to decouple HTTP caching > > classes from HttpClient specific APIs but that would probably require > > opening up a lot of APIs that are presently private. We would need a > > really good reason for doing so. > > Oleg > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > > For additional commands, e-mail: httpclient-users-h...@hc.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
