You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
When the TCP window specified by cordova-plugin-chrome-apps-sockets-tcp is full, the plugin incorrectly reorders packets. (Decreasing bufferSize causes this bug to be more easily triggered)
The following is my reassembly of a packet stream, in which the 3rd and 4th packets are fed to the client in the wrong order. The pipe symbol is the boundary between sequential data packets.
When the TCP window specified by
cordova-plugin-chrome-apps-sockets-tcp
is full, the plugin incorrectly reorders packets. (DecreasingbufferSize
causes this bug to be more easily triggered)This is likely the cause of issue #14.
The following is my reassembly of a packet stream, in which the 3rd and 4th packets are fed to the client in the wrong order. The pipe symbol is the boundary between sequential data packets.
The left side comes from wireshark, the packet trace I've uploaded here: https://github.com/VidaID/cordova-plugin-chrome-apps-sockets-tcp/blob/180-signverify/tcpreorder.pcapng.gz
The right side is the sequence of onReceive data events received by my app, using the
chrome-net
plugin.The erroneous reorderings occur in frames 129 and 131 of the wireshark dump.
Any clue what's going on here?
The text was updated successfully, but these errors were encountered: