# timeout-constraints

[since 2.5]

Ivy, internally, communicates with various remote systems for dealing with module descriptors and artifacts. This is done through various dependency resolvers that are configured in the Ivy settings. This communication typically involves opening a connection to the target system and reading content from those systems. As with all remote communication, certain systems can sometimes be slow or even unavailable on some occasions. `timeout-constraints` in Ivy settings allows you to configure timeouts that can then be used by Ivy while communicating with remote systems.

Note | Although, timeouts are most likely to be used by dependency resolvers, the setting up of timeouts through the use of `timeout-constraints` doesn’t really bother about where those timeouts are used. As such, it’s not an error to have `timeout-constraints` within a Ivy settings file which may never be referred to by any resolver.

## Child elements

Element | Description | Cardinality
--- | --- | ---
timeout-constraint | defines a new timeout-constraint | 0..n

## Examples

    <timeout-constraints>
            <timeout-constraint name="test-timeout-1" connectionTimeout="100" readTimeout="500"/>
            <timeout-constraint name="test-timeout-2" readTimeout="20"/>
            <timeout-constraint name="test-timeout-3" connectionTimeout="400"/>
            <timeout-constraint name="test-timeout-4"/>
    </timeout-constraints>

Defines 4 `timeout-constraint`, each with a name and values for `connectionTimeout` and `readTimeout`. More details about the `timeout-constraint` element is explained in its documentation.