[
https://issues.apache.org/jira/browse/HTTPCORE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513474
]
Oleg Kalnichevski commented on HTTPCORE-101:
--------------------------------------------
Roland
Generally I feel this is very similar to the mutable / immutable HTTP message
interface story we had in the early days of HttpCore. While very nice
conceptually the split of interfaces into immutable and mutable versions proved
too cumbersome in practice. Likewise I feel we are not gaining that much by
making HttpParams immutable per default. Yes, one can do silly things like
modifying parameters concurrently from a different thread but there are other
wonderful ways of screwing things up very badly. We simply have to state
HttpParams are meant to be used in 'write once read many' mode.
I suggest we leave this issue on the back-burner for a while revisit it
sometime later this year before HttpCore goes BETA
Oleg
> Consider read-only HttpParams
> -----------------------------
>
> Key: HTTPCORE-101
> URL: https://issues.apache.org/jira/browse/HTTPCORE-101
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore, HttpCore NIO
> Affects Versions: 4.0-alpha5
> Reporter: Roland Weber
> Assignee: Roland Weber
> Priority: Minor
> Fix For: 4.0-alpha6
>
>
> Consider turning HttpParams into a read-only interface, moving modifiers to
> an extension interface.
> Suggested by Daniel Müller on httpcomponents-dev.
> This will break the following style of updating existing parameters:
> xxx.getParams().setParameter("name", value);
--
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]
