[TIMOB-24385] Windows: Ti.Network.Socket.TCP.readAsync() is not continuous
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2017-02-10T16:05:37.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 6.1.0 |
| Components | Windows |
| Labels | n/a |
| Reporter | Gary Mathews |
| Assignee | Gary Mathews |
| Created | 2017-02-08T12:13:28.000+0000 |
| Updated | 2017-02-13T23:57:11.000+0000 |
Description
- When using
Titanium.Stream.pump() - Titanium.Network.Socket.TCP.readAsync() does not stream data continuously to the callback. Only the first response is received.
- When a connection is terminated the error is not handled elegantly, causing the application to crash.
NOTE: The error parameters in the callbacks for both read and write should be updated accordingly.
master: https://github.com/appcelerator/titanium_mobile_windows/pull/947
Verified fixed, was able to receive multiple responses and when I run the application when no server is running the application no longer crashes. Log output from the application in studio
Logout output from the server running incmdusingnode index.js*Environment*