On 08/13/2014 11:07 AM, Markus Armbruster wrote:
Daniel H Barboza writes:
On 08/13/2014 09:39 AM, Daniel H Barboza wrote:
On 08/13/2014 06:15 AM, Markus Armbruster wrote:
Daniel Henrique Barboza writes:
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the
Daniel H Barboza writes:
> On 08/13/2014 09:39 AM, Daniel H Barboza wrote:
>>
>> On 08/13/2014 06:15 AM, Markus Armbruster wrote:
>>> Daniel Henrique Barboza writes:
>>>
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and
On 08/13/2014 09:39 AM, Daniel H Barboza wrote:
On 08/13/2014 06:15 AM, Markus Armbruster wrote:
Daniel Henrique Barboza writes:
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to s
On 08/13/2014 06:15 AM, Markus Armbruster wrote:
Daniel Henrique Barboza writes:
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the con
Daniel Henrique Barboza writes:
> The curl hardcoded timeout (5 seconds) sometimes is not long
> enough depending on the remote server configuration and network
> traffic. The user should be able to set how much long he is
> willing to wait for the connection.
>
> Adding a new option to set this
On 08/12/2014 12:36 PM, Eric Blake wrote:
On 08/12/2014 08:35 AM, Daniel Henrique Barboza wrote:
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wa
On 08/12/2014 08:35 AM, Daniel Henrique Barboza wrote:
> The curl hardcoded timeout (5 seconds) sometimes is not long
> enough depending on the remote server configuration and network
> traffic. The user should be able to set how much long he is
> willing to wait for the connection.
>
> Adding a n
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the connection.
Adding a new option to set this timeout gives the user this
flexibility. The
