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
Hi,
While I was monitoring network traffic on my device I saw that every 15 seconds there are acks being sent between the longpoll client and server.
Is this the intentional behavior?
The activity does not need to be ‘silent’ until a timeout occurs or a disconnect or a publish? @jcuga
The text was updated successfully, but these errors were encountered:
This occurs at the TCP/transport level, before the HTTP/application level. So there will be no http data being sent, but you will see at the lower TCP level some zero-data ACKs that are part of the tcp-keepalive. The keep alive time is configurable usually at the OS level, not at a per-socket or per-application level.
Without keep-alives, there'd be no way for each side of the connection to know when a connection gets dropped.
This occurs at a lower, more fundamental level than HTTP and golongpoll specifically. I'd recommend looking at the traffic in wireshark or similar tool to verify that this is indeed zero-data keepalive traffic if you are concerned.
To your question about being "silent" until there is data (or a longpoll-timeout)--at the HTTP/application level, yes, there should be no data/communication.
Hi,
While I was monitoring network traffic on my device I saw that every 15 seconds there are acks being sent between the longpoll client and server.
Is this the intentional behavior?
The activity does not need to be ‘silent’ until a timeout occurs or a disconnect or a publish?
@jcuga
The text was updated successfully, but these errors were encountered: