hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HTTPCORE-100) revise HttpContext hierarchy
Date Fri, 20 Jul 2007 19:44:06 GMT

     [ https://issues.apache.org/jira/browse/HTTPCORE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Roland Weber updated HTTPCORE-100:

    Attachment: 2k7-07-20-HttpCtxt-take-1.txt

Here is take 1, just addressing core and nio for now.
I've chosen the interface version. With three methods for each attribute (get/set/remove),
it just felt too clumsy to code all those null-checks for arguments, and to write the javadocs.

What do you think?


> revise HttpContext hierarchy
> ----------------------------
>                 Key: HTTPCORE-100
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-100
>             Project: HttpComponents Core
>          Issue Type: Improvement
>          Components: HttpCore
>    Affects Versions: 4.0-alpha5
>            Reporter: Roland Weber
>            Assignee: Roland Weber
>             Fix For: 4.0-alpha6
>         Attachments: 2k7-07-20-HttpCtxt-take-1.txt
> (posted on the httpcomponents-dev list)
> I don't like the current HttpContext hierarchy. We have:
> HttpContext - interface, some attribute name constants
> HttpExecutionContext - implementation, more attrib names
> SyncHttpExecutionContext - extended implementation
> HttpClientContext - more attribute names
> We solved this much better with HttpParams, where
> all the attribute names are defined separately
> instead of cluttering the interface or being spread
> around in implementation classes.
> I would like to move the attribute name constants
> either to separate interfaces defining only constants,
> or to isolated classes with static helper methods like
> we have them for HttpParams. The HttpContext hierarchy
> in core/client would be streamlined to the interface
> and the two implementations.

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