[
https://issues.apache.org/jira/browse/HTTPCLIENT-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073837#comment-17073837
]
Oleg Kalnichevski commented on HTTPCLIENT-2070:
-----------------------------------------------
> Would it be possible to have httpclient finding an implementation of put/get
>not using object serialization ?
Java object serialization was chosen for no reason other than its simplicity.
There is nothing stopping us from removing in favor of something else (as long
as it does not come at the expense of having a mandatory external dependency.
Oleg
> BasicAuthCache not to use object serialization
> ----------------------------------------------
>
> Key: HTTPCLIENT-2070
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2070
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Alex Dettinger
> Priority: Major
>
> Today, BasicAuthCache is using object serialization in [put/get
> methods|https://github.com/apache/httpcomponents-client/blob/master/httpclient5/src/main/java/org/apache/hc/client5/http/impl/auth/BasicAuthCache.java#L91..L93].
> However, object serialization is not supported with [quarkus native
> mode|https://quarkus.io/guides/building-native-image] and folk ends up
> removing this part.
> Folks ends up removing serialization by [native code
> override|https://github.com/quarkusio/quarkus/blob/master/extensions/elasticsearch-rest-client/runtime/src/main/java/io/quarkus/elasticsearch/restclient/runtime/graal/Substitute_RestClient.java#L93..L114].
> Would it be possible to have httpclient finding an implementation of put/get
> not using object serialization ?
> What is the consequence of removing the serialization/deserialization ?
> Thread safety issue ? persistence issue ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
