You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Julien Vermillard (JIRA)" <ji...@apache.org> on 2010/01/19 14:49:54 UTC
[jira] Resolved: (DIRMINA-715) Ability to set timeouts for
NioSocketConnector.connect()
[ https://issues.apache.org/jira/browse/DIRMINA-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien Vermillard resolved DIRMINA-715.
---------------------------------------
Resolution: Won't Fix
the API is frozen, you still can change the time out before each connection.
> Ability to set timeouts for NioSocketConnector.connect()
> --------------------------------------------------------
>
> Key: DIRMINA-715
> URL: https://issues.apache.org/jira/browse/DIRMINA-715
> Project: MINA
> Issue Type: Wish
> Components: Core
> Affects Versions: 2.0.0-M5
> Reporter: Roger Kapsi
>
> The connect() method in MINA 1.x had an argument for a SocketConnectorConfig object that would allow the user to specify a custom timeout for each call.
> In MINA 2.x there is only a per NioSocketConnector instance timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.