[
https://issues.apache.org/jira/browse/HTTPCORE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487410
]
Oleg Kalnichevski commented on HTTPCORE-65:
-------------------------------------------
You do not want the default value, you just do not read it, no? What specific
use case do you have in mind?
Oleg
> Allow for explicit null in HttpContext and HttpParams
> -----------------------------------------------------
>
> Key: HTTPCORE-65
> URL: https://issues.apache.org/jira/browse/HTTPCORE-65
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.0-alpha4
> Reporter: Roland Weber
> Priority: Minor
>
> Both HttpContext and HttpParams support hierarchies. The current
> implementations ([Sync]HttpExecutionContext, BasicHttpParams) do allow for
> overriding a parent/default value with another value, but they do not allow
> for overriding with null. Implementation alternatives:
> - lookup the map entry instead of the value, do not fall back to
> parent/default if an entry is there with a null value
> - use a dedicated constant to represent an explicit null value
> cheers,
> Roland
--
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]