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

Pierre edited comment on SSHD-162 at 5/5/12 7:47 AM:
-----------------------------------------------------

Updated patch:
- since we are not reusing the executor when it is not passed by the creator of 
the InvertedShellWrapper, use a fixed thread pool of one thread instead of a 
cached pool
- use a NamePreservingRunnable to set the name of the Thread while running the 
IO pumps
                
      was (Author: pepoirot):
    Update patch:
- since we are not reusing the executor when it is not passed by the creator of 
the InvertedShellWrapper, use a fixed thread pool of one thread instead of a 
cached pool
- use a NamePreservingRunnable to set the name of the Thread while running the 
IO pumps
                  
> Allow the configuration of InvertedShellWrapper's thread pool
> -------------------------------------------------------------
>
>                 Key: SSHD-162
>                 URL: https://issues.apache.org/jira/browse/SSHD-162
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 0.6.0
>            Reporter: Pierre
>            Priority: Minor
>              Labels: thread
>         Attachments: SSHD-162.patch
>
>
> InvertedShellWrapper spawns a new thread for pumping the shell I/O. It would 
> be more flexible to allow the specification of an Executor, so that the user 
> can customise how the new thread is allocated (for example, to allow its 
> allocation from a cached thread pool or a pool with a bounded number of 
> threads).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to