[
https://issues.apache.org/jira/browse/DIRMINA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Webb resolved DIRMINA-527.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-M2
I applied the associated patch after reviewing the patch. This only adds to
the precision of the timeout. The methods that dealt with getting and setting
the connection timeout in seconds have been deprecated and a note in the
javadoc says that the millisecond-based methods should be used.
> should be able to set connect timeout in milliseconds
> -----------------------------------------------------
>
> Key: DIRMINA-527
> URL: https://issues.apache.org/jira/browse/DIRMINA-527
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0.8, 1.1.5, 2.0.0-M1
> Reporter: Sangjin Lee
> Assignee: Mark Webb
> Fix For: 2.0.0-M2
>
> Attachments: DIRMINA-527.patch
>
>
> Currently, IoConnector allows setting connect timeouts only in seconds. The
> minimum value of allowed connect timeout is 1 second. There are cases where
> one needs to have a shorter connect timeout than 1 second and will finer
> granularity than seconds.
> I suggest introducing the ability to set connect timeout in milliseconds and
> deprecating the getter/setter in seconds in favor of the ms getter/setter.
> See the discussion thread at
> http://www.nabble.com/connect-timeout-to15281787s16868.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
