Re^8: How to make an HTTP request with an equivalent of curl's --max-time?

There is very little "explanation" in your reply, which (if your intention was to provide additional information / suggestions to the OP) should either be posted under the original post, or should simply state the fact that it is addressed to someone else that the author of the post you are replying to.

If you would take the time to read the docs I've linked to, you would notice that the OP probably needs both the maximum time and the socket timeout option. The latter will be needed to satisfy the API requirements, while the former could be necessary to satisfy OP's requirement to "manage the amount of data received by the script".

Not everything is "obvious and self-evident", but taking the time to read the nodes you are replying to, and taking the time to make your replies clear in their meaning and relevant to the point would be a step in this direction.

- Luke

Comment on Re^8: How to make an HTTP request with an equivalent of curl's --max-time?

Replies are listed 'Best First'.
Re^9: How to make an HTTP request with an equivalent of curl's --max-time? by Anonymous Monk on Jan 14, 2015 at 10:55 UTC
That is like a good idea	[reply]
Re^9: How to make an HTTP request with an equivalent of curl's --max-time? by Cody Fendant (Hermit) on Jan 14, 2015 at 22:24 UTC
Thanks for that explanation. Yes, it's true that I need both kinds of timeout. Currently I hold the connection open for 180 seconds which gives me 35-40 MB of tweets in a roughly 10,000-line file. If I wanted more, I'd increase that value. The other kind of timeout would presumably cause it to close down if the network or Twitter were having problems and I'd get nothing, but that's a different case.	[reply]