[
https://issues.apache.org/jira/browse/HTTPCLIENT-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004316#comment-16004316
]
yair ogen commented on HTTPCLIENT-1826:
---------------------------------------
oh. that's bad,
Adding API is exactly aligned with Open Close Principle.
You don't have that many implementations - do you? the PR added implementation
where needed.
People do this all the time. You should never freeze an interface in the sense
of forbid additions. you should prevent changing names or removing APIs. That
DOES break backward compatibility.
> Async Builder should include setting a ExecutorService
> ------------------------------------------------------
>
> Key: HTTPCLIENT-1826
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1826
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: yair ogen
>
> Currently you only expose setting ThreadFactory. Not very useful if a user
> wants to send in a different thread pool altogether.
> We must have an option to pass in thread pools especially if we want this
> async work to co-exist in the same pool as other tasks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
