hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Mays (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HTTPCLIENT-427) Implement a cache to perform real request only when needed
Date Mon, 03 May 2010 18:23:59 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863447#action_12863447
] 

David Mays commented on HTTPCLIENT-427:
---------------------------------------

For the SizeLimitedResponseReader and OptionsHttp11Response, these are "new" for every request,
and so should not be accessed by multiple threads unless someone was doing something very
unusual in their client code.

The counters in CachingHttpClient are being updated to AtomicLong.

The tricky bit is the CacheEntry.

I'm thinking that the atomicity there should be in the updates to the cache, rather than the
entry itself. We already have this notion with the HttpCacheUpdateCallback, which enables
atomic updates to the cache. The key is preventing existing instances of a CacheEntry from
being updated while someone is reading one. I believe we have a handle on how to make this
happen, so we are working on it now.

What do you consider the top priority items to complete before you consider this ready for
release? Specifically, is the CacheEntry physical representation something you consider gating
for release, or can that go as-is for now?

Dave

> Implement a cache to perform real request only when needed
> ----------------------------------------------------------
>
>                 Key: HTTPCLIENT-427
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-427
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient
>         Environment: Operating System: Linux
> Platform: PC
>            Reporter: Marc Guillemot
>             Fix For: 4.1 Alpha2
>
>         Attachments: caching_client.zip, httpclient-cache.zip
>
>
> Browsers may cache received content according to the values of different
> response headers. It would be great if HttpClient could do the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message