You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2018/08/06 11:47:00 UTC
[jira] [Resolved] (HTTPCORE-536) duplicate connect method could be
extract
[ https://issues.apache.org/jira/browse/HTTPCORE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCORE-536.
----------------------------------------
Resolution: Fixed
Fix Version/s: 5.0-beta3
> duplicate connect method could be extract
> -----------------------------------------
>
> Key: HTTPCORE-536
> URL: https://issues.apache.org/jira/browse/HTTPCORE-536
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore NIO
> Reporter: silver9886
> Priority: Major
> Fix For: 5.0-beta3
>
>
> DefaultConnectingIOReactor and DefaultListeningIOReactor connect method are same.
> create abstractDefaultIOReactor class,put the connect code to the abstract class.
> AsyncServer and AsyncRequester connect method are same.
> create abstractAsyncServerandRequester class,put the connect code to the abstract class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org