[
https://issues.apache.org/jira/browse/HTTPCLIENT-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-916:
-----------------------------------------
Attachment: HTTPCLIENT-916-tests.patch
As far as I know a class does not have to comply with the Java Bean spec in
order to be Serializable. Both HttpHost and HttpVersion are valid Serializable
while they do not have a no arg constructor and have final fields.
I always wanted to keep persistence aspects out of HttpClient but, if there is
popular demand for it, I can live with making BasicUserPrincipal,
NTUserPrincipal, as well as BasicClientCookie, BasicClientCookie2, and
BasicCookieStore Serializable.
Oleg
> RFE: Make Credentials Serializable
> ----------------------------------
>
> Key: HTTPCLIENT-916
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-916
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpAuth, HttpClient, HttpCookie
> Affects Versions: 4.0.1
> Reporter: Daniel Gredler
> Priority: Minor
> Fix For: 4.1 Alpha2
>
> Attachments: HTTPCLIENT-916-tests.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> I've been working on upgrading the HtmlUnit library to use HttpClient 4, and
> I've realized that we could eliminate some hackish internal code if
> Credentials instances were Serializable. I don't really see a downside, and
> this would be a huge convenience for us.
> The change would involve making the org.apache.http.auth.Credentials
> interface extend Serializable, and having
> org.apache.http.auth.BasicUserPrincipal and
> org.apache.http.auth.NTUserPrincipal implement Serializable (plus
> serialVersionUIDs where appropriate, I guess).
--
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: [email protected]
For additional commands, e-mail: [email protected]
