|Home > Generic function call interface > IrisRpc (RPC transport layer) > TCP considerations|
TCP sockets should be created with the
keep-alive option, if possible. If not possible, the side that does not support
keep-alive should call the
instance_ping(instId=0) function, which does nothing, 3600s after the last function call. The default TCP
keep-alive time is 7200s, or 2 hours, for Linux and Windows.
The two crossed JSON RPC 2.0 client and JSON RPC 2.0 server pairs share a single TCP connection. Function calls, responses, and notifications are sent over the same TCP connection in both directions.