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.
Dear all,
This is a great cordova plugin. It has reliably worked for me in most situations.
However, if I have a long response message the response is cut arbitrarily and another onReceive Event is triggered with the rest of the message... (very long messages are even cut into multiple pieces). This wouldn't be a problem if there would be some kind of mechanism to check what should get together.
If it is unclear what I mean, I can provide an example where a IRC server is called and the users of a channel are queried. Effectively this is a long string. The response (depending on the size) is cut into various pieces. There is however no indication on how to glue these together other than information inside the message itself, which is very error prone...
The text was updated successfully, but these errors were encountered:
I'm seeing this problem too, did you find any solution?
This seems to happen whenever the receive buffer gets full. You can make it trigger more easily by decreasing the bufferSize parameter in src/android/ChromeSocketsTcp.java.
Dear all,
This is a great cordova plugin. It has reliably worked for me in most situations.
However, if I have a long response message the response is cut arbitrarily and another onReceive Event is triggered with the rest of the message... (very long messages are even cut into multiple pieces). This wouldn't be a problem if there would be some kind of mechanism to check what should get together.
If it is unclear what I mean, I can provide an example where a IRC server is called and the users of a channel are queried. Effectively this is a long string. The response (depending on the size) is cut into various pieces. There is however no indication on how to glue these together other than information inside the message itself, which is very error prone...
The text was updated successfully, but these errors were encountered: