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 Nov 28, 2018. It is now read-only.
I am a bit surprised that this is not working and I am wondering if it is me doing something wrong.
Problem is when receiving a large message (plain/text), information is processed and the Frame is created even if the message is not completed (the socket would have had received eventually all information as I have checked) but in the first data event is processed without contemplating the case of not being complete.
Is this some sort of configuration issue, or is it just not coded at the moment?
If it is the second case I would probably give it a go to try to fix it.
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
I am a bit surprised that this is not working and I am wondering if it is me doing something wrong.
Problem is when receiving a large message (plain/text), information is processed and the Frame is created even if the message is not completed (the socket would have had received eventually all information as I have checked) but in the first data event is processed without contemplating the case of not being complete.
Is this some sort of configuration issue, or is it just not coded at the moment?
If it is the second case I would probably give it a go to try to fix it.
Regards,
The text was updated successfully, but these errors were encountered: