KEEPALIVE (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle" | <span class="pageSubtitle">KEEPALIVE xxxx — number of seconds to hold open TCP/IP connection</span> | ||
<var>KEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | <var>KEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
| Line 5: | Line 5: | ||
The <var>KEEPALIVE</var> parameter indicates the number of seconds a TCP/IP connection is to be held open after an HTTP request on that connection. <var>KEEPALIVE</var> must be followed by a single number between 0 and 32767, which indicates the maximum number of seconds to hold the connection open. A setting of 0 means no keep-alive. | The <var>KEEPALIVE</var> parameter indicates the number of seconds a TCP/IP connection is to be held open after an HTTP request on that connection. <var>KEEPALIVE</var> must be followed by a single number between 0 and 32767, which indicates the maximum number of seconds to hold the connection open. A setting of 0 means no keep-alive. | ||
For <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports, this parameter tells | For <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports, this parameter tells <var class="product">[[Janus Web Server]]</var> to keep HTTP connections from a client (often a browser) open for the indicated period of time. For <var>[[JANUS DEFINE#type|CLSOCK]]</var> ports, <var>KEEPALIVE</var> tells <var class="product">[[Janus Sockets]]</var> to keep an HTTP connection to a web server open for the indicated period of time, and to reuse that connection for other requests to the same server. | ||
Keep-alive connections, more often referred to as '''persistent connections''', can reduce network traffic and, more significantly, HTTP request latency. Both of these benefits are magnified for SSL connections, where each HTTP request requires a TCP/IP and SSL connection-establishment handshake. | Keep-alive connections, more often referred to as '''persistent connections''', can reduce network traffic and, more significantly, HTTP request latency. Both of these benefits are magnified for SSL connections, where each HTTP request requires a TCP/IP and SSL connection-establishment handshake. | ||
For a | For a <var class="product">Janus Web Server</var> connection to be held open, the client/browser must indicate that it supports HTTP keep-alives. For a <var class="product">Janus Sockets</var> connection to be held open, the web server must indicate that it supports HTTP keep-alives. Most modern browsers and web servers support and take advantage of keep-alives. | ||
The <var>KEEPALIVE</var> parameter is valid only for | The <var>KEEPALIVE</var> parameter is valid only for <var class="product">Janus Web Server</var> and for <var class="product">Janus Sockets</var> <var>CLSOCK</var> ports used for HTTP traffic (that is, not for SMTP connections). It is '''not''' valid for <var class="product">Janus Sockets</var> <var>SRVSOCK</var> or <var>[[JANUS DEFINE#type|DEBUGGERCLIENT]]</var> ports and '''not''' valid for SMTP connections. | ||
<var>KEEPALIVE</var> is new as of | <var>KEEPALIVE</var> is new as of <var class="product">Sirius Mods</var> Version 6.8. | ||
==See also== | ==See also== | ||
Latest revision as of 22:17, 16 April 2013
KEEPALIVE xxxx — number of seconds to hold open TCP/IP connection
KEEPALIVE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
The KEEPALIVE parameter indicates the number of seconds a TCP/IP connection is to be held open after an HTTP request on that connection. KEEPALIVE must be followed by a single number between 0 and 32767, which indicates the maximum number of seconds to hold the connection open. A setting of 0 means no keep-alive.
For WEBSERV ports, this parameter tells Janus Web Server to keep HTTP connections from a client (often a browser) open for the indicated period of time. For CLSOCK ports, KEEPALIVE tells Janus Sockets to keep an HTTP connection to a web server open for the indicated period of time, and to reuse that connection for other requests to the same server.
Keep-alive connections, more often referred to as persistent connections, can reduce network traffic and, more significantly, HTTP request latency. Both of these benefits are magnified for SSL connections, where each HTTP request requires a TCP/IP and SSL connection-establishment handshake.
For a Janus Web Server connection to be held open, the client/browser must indicate that it supports HTTP keep-alives. For a Janus Sockets connection to be held open, the web server must indicate that it supports HTTP keep-alives. Most modern browsers and web servers support and take advantage of keep-alives.
The KEEPALIVE parameter is valid only for Janus Web Server and for Janus Sockets CLSOCK ports used for HTTP traffic (that is, not for SMTP connections). It is not valid for Janus Sockets SRVSOCK or DEBUGGERCLIENT ports and not valid for SMTP connections.
KEEPALIVE is new as of Sirius Mods Version 6.8.