[
https://issues.apache.org/jira/browse/HTTPCORE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCORE-133:
---------------------------------------
Affects Version/s: 4.0-beta1
I am going to implement Cloneable for all classes that already have a #copy
method or where ability to produce shallow copies may be useful. This said, I
am sure cloning entities makes sense (at least to me). Why would you want that?
Besides, streaming entities simply cannot be cloned because they are
essentially read-once.
Oleg
> Clone support
> -------------
>
> Key: HTTPCORE-133
> URL: https://issues.apache.org/jira/browse/HTTPCORE-133
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.0-beta1
> Reporter: David Byrne
> Priority: Minor
>
> It would be nice to have a clone method for some of the classes that don't
> have getters & setters exposed for all of their fields. Where relevant, the
> clone method could be in the interface, so that it doesn't matter which
> implementing class is being used. If I want to clone an entity, I can clone a
> entity and not figure out if it's UrlEncodedFormEntity, FileEntity, etc. So
> far, HttpEntity is the only interface in HttpCore that I've wanted to clone.
> I'm going to submit another ticket for client.
> Thanks,
> David Byrne
--
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]
