timeout event, and timeout option implemented. added docs & example #130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was serially testing GET's on a million websites, and gradually came across my test app stalling with the same pattern.
It turned out that restler has/had no option for timeout. This is a show-stopper for large/production scenarios.
eg: The following code, stalls forever, without throwing an error or
infact it did not emit any known events either. namely error or abort.
I also saw previous mentions requesting timeout feature for restler.
eg: #3 one of the oldest open bugs/issues.
So i went ahead, forked and fixed this.
My commit includes :
Here's an example.
Will love to see this reviewed for a possible merge.
~Bosky @bhaskerkode