You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (Jira)" <ji...@apache.org> on 2022/05/07 07:02:00 UTC
[jira] [Resolved] (HTTPCLIENT-2214) MemcachedHttpAsyncCacheStorage should use MemcachedClientIF interface
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-2214.
-------------------------------------------
Resolution: Fixed
[~dkrompet] Please see HTTPCLIENT-2204 for detailed explanation why this is not a bug.
Oleg
> MemcachedHttpAsyncCacheStorage should use MemcachedClientIF interface
> ---------------------------------------------------------------------
>
> Key: HTTPCLIENT-2214
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2214
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 5.0, 5.1, 5.1.2, 5.1.3
> Reporter: Dillon Krompetz
> Priority: Minor
>
> Similar to https://issues.apache.org/jira/browse/HTTPCLIENT-2202
> There also seems to have been a similar regression from 4.x to 5.x in terms of using hard implementations of MemcachedClient object over interface MemcachedClientIF.
> Changing to use MemcachedClientIF would again here be backwards compatible due to Memcached.
> {code:java}
> public class MemcachedHttpAsyncCacheStorage extends AbstractBinaryAsyncCacheStorage<CASValue<Object>> {
> private final MemcachedClient client;
> private final KeyHashingScheme keyHashingScheme;
> public MemcachedHttpAsyncCacheStorage(final InetSocketAddress address) throws IOException {
> this(new MemcachedClient(address));
> }
> ...{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org