[
https://issues.apache.org/jira/browse/DIRMINA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577025#action_12577025
]
Trustin Lee commented on DIRMINA-527:
-------------------------------------
For example, we could start from 1000ms selector timeout at the first time. If
a user specifies a connect timeout value smaller than 1000ms, we can adjust the
1000ms to the connect timeout value specified (or its half). By doing so, we
can minimize unnecessary CPU consumption, because most users will use the
timeout value of 60 seconds or something similar to that. If a user wants a
millisecond-level timeout (e.g. 9ms), then he will pay for what he or she
wants, but it's not the case for most people.
> 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.
