hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ortwin Glück (JIRA) <j...@apache.org>
Subject [jira] Commented: (HTTPCORE-129) Immutable request/response
Date Tue, 06 Nov 2007 21:16:51 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540574

Ortwin Glück commented on HTTPCORE-129:

Yes, it may be hard to guarantee read-only access on composite objects if you don't want to
copy in getters/setters. For the Iterator at least there is the Enumeration read-only alternative.

> 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: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org

View raw message