Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We are pushing around 1600 bytes status information from the module (BCM943341) over WiFi to the webSocket server hosted by EC2 every second. Also, the server as part of handshake sends a ping every 10 seconds, to which the module responds with a pong.
We have a 130 bytes command that is sent by the server to the web socket client on the module. This can arrive any time. However, we have observed that this message is sometimes delayed and many a time, it is just not received, even though the server gets an ACK for every such message sent.
I wish to know:
(1) do we share tx/rx buffers at the lower layer of tcp socket send/recv?
(2) what is the min/max tx/rx messages that can be sent reliably with moderate to lower latency ~ 1second?