[
https://issues.apache.org/jira/browse/HTTPCORE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540416
]
Oleg Kalnichevski commented on HTTPCORE-129:
--------------------------------------------
Stojce
Odi is right. We decided to do away with immutable / mutable message interfaces
because, while being very nice from the conceptual standpoint, the use of
immutable interfaces led to ugly downcasts all over the place
http://marc.info/?l=httpclient-commons-dev&w=2&r=1&s=mutability+and+immutability&q=b
We might still turn things around and leave the default interfaces mutable but
in additional provide their immutable counterparts for those cases where
message immutability can be useful
HttpMessage extends HttpImmutableMessage
Opinions?
Oleg
> Immutable request/response
> --------------------------
>
> Key: HTTPCORE-129
> URL: https://issues.apache.org/jira/browse/HTTPCORE-129
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.0-beta1
> Reporter: Stojce Dimski
> Priority: Minor
>
> There are many cases where user would just 'consume' response and would not
> have to modify nothing es. received response...
> With 2 interfaces and guideline to use a immutable version for polymorphic
> variables compiler would catch any error pretty soon...
> Is there some possibility to have e immutable request/response objects as in:
> https://svn.safehaus.org/repos/asyncweb/trunk/core/src/main/java/org/safehaus/asyncweb/common/HttpMessage.java
> https://svn.safehaus.org/repos/asyncweb/trunk/core/src/main/java/org/safehaus/asyncweb/common/MutableHttpMessage.java
--
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]
