keepalive

KeepAlive strategy is widely used in communications system .

KeepAlive机制在通信中使用极其广泛。

Should you consider using HTTP Keepalive for best performance when communicating with the remote end ?

与远程终端通信时，应该考虑使用HTTPKeepalive实现最佳性能？

For our sample application , we implemented HTTP Keepalive in the TCAP interface to significantly improve performance .

对于我们的样例应用程序，我们在TCAP接口中实现HTTPKeepalive来大幅提高性能。

Therefore , the same socket connection is kept alive and re-used with the keepAlive = true setting .

设置keepAlive=true，因而，同一个套接字连接始终保持活动状态，并可重用。

HTTP Keepalive solves this performance problem by considerably reducing the overhead associated with establishing and tearing down TCP connections .

HTTPKeepalive通过大幅减少建立和终止TCP连接的相关开销来解决这个性能问题。

Long keepalive : The keep-alive interval

longkeepalive：保持活动的间隔

Opening and closing of HTTP connections is still required , which may be expensive in the case of non-persistent connection mode ( keepAlive = false ) .

仍然需要打开和关闭HTTP连接，如果采用的是非持久连接模式（keepAlive=false），那么这种方法的代价可能极高。

Considering the influences of Keepalive message and Update message , we deduce the probability expression of session failure and give a method to improve the IBGP session reliability .

分别在考虑Keepalive报文和Update报文对会话可靠性影响的基础上，推导了IBGP会话失败概率表达式，给出了一种可以提高IBGP会话可靠性的方法。