[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999713#comment-15999713
 ] 

yair ogen edited comment on HTTPCLIENT-1826 at 5/7/17 7:05 AM:
---------------------------------------------------------------

[~olegk] 
Thanks. I don't see how this help me? I am asking for allowing injection of an 
executor service in order to use my own thread pool.
Thread Factory in itself doesn't help me. Once the thread is created I don't 
have and interface with it. My own Executor Service does give me the 
flexibility I need.

so, I don't think this ticked is "Fixed".


was (Author: yairogen):
[~olegk]Thanks. I don't see how this help me? I am asking for allowing 
injection of an executor service in order to use my own thread pool.
Thread Factory in itself doesn't help me. Once the thread is created I don't 
have and interface with it. My own Executor Service does give me the 
flexibility I need.

so, I don't think this ticked is "Fixed".

> Async Builder should include setting am ExecutorService
> -------------------------------------------------------
>
>                 Key: HTTPCLIENT-1826
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1826
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>            Reporter: yair ogen
>             Fix For: 5.0 Alpha2
>
>
> 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]

Reply via email to