[
https://issues.apache.org/jira/browse/IVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097975#comment-16097975
]
ASF GitHub Bot commented on IVY-735:
------------------------------------
Github user jaikiran commented on the issue:
https://github.com/apache/ant-ivy/pull/54
>> VsftpRepository has DEFAULT_READ_TIMEOUT and DISCONNECT_COMMAND_TIMEOUT;
would that require an additional timeout attribute?
I had a look at this. Given that there's currently no way it can be
configured on the resolver itself and that it looks more like an internal
usage, I wouldn't expose this as an additional timeout attribute, especially
since it's very specific to this resolver.
In general, I think the resolver(s) should use the named
`timeout-constraint` for the common timeout concepts (like connection timeout
and read timeout) and if necessary specify additional timeout details that are
very specific to that resolver as specific attributes on the resolver's element
itself.
> Timeout should be able to be specified
> --------------------------------------
>
> Key: IVY-735
> URL: https://issues.apache.org/jira/browse/IVY-735
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0-beta-1
> Reporter: Testo Nakada
> Assignee: jaikiran pai
> Attachments: 0001-Add-timeout-support-for-HTTP-requests.patch
>
>
> It's currently not possible to provide timeout for resolver. For example,
> yesterday ibiblio is really slow. I waited almost forever just to know that
> there is something wrong with ibiblio. It would be nice if I can specify
> timeout so that i can fail over to some other resolvers in my chain resolver.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
