[
https://issues.apache.org/jira/browse/HTTPCLIENT-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-2204.
-------------------------------------------
Fix Version/s: (was: 5.2-alpha2)
Resolution: Invalid
MemcachedClientIF is not flexible enough for non-blocking operations. Async
client implementations will have to continue using MemcachedClient. I also
partially reverted HTTPCLIENT-2202.
Oleg
> MemcachedAsyncHttpCacheStorage should use MemcachedClientIF interface
> ----------------------------------------------------------------------
>
> Key: HTTPCLIENT-2204
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2204
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 5.0, 5.1, 5.1.1, 5.1.2, 5.1.3
> Reporter: Robert Kennedy
> Priority: Minor
>
> Similar to HTTPCLIENT-2202
>
> There appears to be a regression from 4.x to 5.x in which
> [MemcachedHttpAsyncCacheStorage|https://github.com/apache/httpcomponents-client/blob/master/httpclient5-cache/src/main/java/org/apache/hc/client5/http/impl/cache/memcached/MemcachedHttpAsyncCacheStorage.java]
> now requires the MemcachedClient object instead of the interface
> MemcachedClientIF. The class doesn't use any functionality outside of the
> interface, so why require anything higher than the interface?
> Changing to use MemcachedClientIF would be backward compatible since
> MemcachedClient implements this interface already.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
