[ https://issues.apache.org/jira/browse/DIRAPI-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radovan Semancik resolved DIRAPI-378. ------------------------------------- Resolution: Fixed > Finer-grain timeouts > -------------------- > > Key: DIRAPI-378 > URL: https://issues.apache.org/jira/browse/DIRAPI-378 > Project: Directory Client API > Issue Type: Improvement > Affects Versions: 2.1.0 > Reporter: Radovan Semancik > Priority: Major > > The API has only one _timeout_ value that is applied to everything. However, > while some operations can take >100ms, we would like much shorter timeouts > for connect, bind or close operations (e.g. to quickly detect connection > problems and fail over). > More granular timeouts are in order: connect timeout, write/read operation > timeout, close timeout, send timeout. > For convenience and compatibility, there is still "global timeout" that works > in the same way as in 2.1.0 - it sets all the operation-specific timeouts. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org