Log In
07/15/2024
Offline
In reverse connection ua-server initiates connection to ua-client by sending RHEL message.
What is the preferable way to determine the connection loss so ua server can resend RHEL message to the client?
Can we enable tcp keep-alive on ua-server side?
Or should we have some configurable timeout on ua-server side like "timeout of no client messages received" ?
Or may be ua-server shall once in a sec try to open socket to the client and this way monitor connection loss?
Or may be ua-server should wait for session timeout to pass?
Any other way?
05/30/2017
Offline
You would depend on TCP level errors to determine that the socket has been lost.
This could mean long time outs or other error reporting delays that occur when relying on TCP stack error notifications.
The spec provides no recommendations when it comes to setting TCP socket properties but perhaps it should.
Can you add a mantis issue for Part 6 with some suggestions for spec additions:
1 Guest(s)
Usage Policy