[TIMOB-7992] Socket.TCP: Add support for more granular timeouts
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-15T18:31:47.000+0000 |
| Affected Version/s | Release 2.0.0 |
| Fix Version/s | n/a |
| Components | TiAPI |
| Labels | tbs-2.1.0 |
| Reporter | Marshall Culpepper |
| Assignee | Eric Merriman |
| Created | 2012-03-14T10:30:53.000+0000 |
| Updated | 2017-06-15T18:31:47.000+0000 |
Description
We've recently had a few community PRs that have brought up the fact that our current TCP socket implementation doesn't give enough control over timeouts in specific situations. We need to come up with a set of APIs that allow more granular control over timeouts for things like accept, soTimeout, etc.
Here's the links to the original community PRs:
https://github.com/appcelerator/titanium_mobile/pull/1425
https://github.com/appcelerator/titanium_mobile/pull/1426
Closing ticket due to time passed and lack of progress in the past few years. Any problems, please file a new ticket.