You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Roland Weber (JIRA)" <ji...@apache.org> on 2007/04/06 21:07:32 UTC
[jira] Commented: (HTTPCORE-64) Ensure consistent use of
HttpContext and HttpParams
[ https://issues.apache.org/jira/browse/HTTPCORE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487316 ]
Roland Weber commented on HTTPCORE-64:
--------------------------------------
And document that HttpParams.setDefaults() is for use by the framework only, not for applications. If applications pass in a hierarchy of params, and the request executor or some other component links in new defaults, unexpected behavior results. In the worst case, we might end up with a circular parent relationship.
setDefaults(null) is the only operation permitted to applications, at least for params that are passed to the framework.
cheers,
Roland
> Ensure consistent use of HttpContext and HttpParams
> ---------------------------------------------------
>
> Key: HTTPCORE-64
> URL: https://issues.apache.org/jira/browse/HTTPCORE-64
> Project: HttpComponents Core
> Issue Type: Task
> Reporter: Oleg Kalnichevski
> Assigned To: Oleg Kalnichevski
> Fix For: 4.0-alpha5
>
>
> (1) Review the code base and ensure HttpContext and HttpParams interfaces are used consistently across HttpCore
> (2) Use non-synchronized instances of HttpContext and HttpParams in those cases when they can be accessed by a single thread only
--
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