[
https://issues.apache.org/jira/browse/HTTPCORE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-129.
----------------------------------------
Resolution: Won't Fix
Stojce,
I am closing this issue as WONTFIX for now as no one seems interested in
working on this improvement. Feel free to re-open it if you intend to submit a
patch at some point. By the way HttpCore NIO is now Java 1.5 based as you
wanted. Feedback would be very welcome ;-)
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]
