Abstract: In an embodiment, techniques for sustaining session connections are provided. The techniques send heartbeat messages when not sending a message may cause the session connection to close because of a timeout condition. Heartbeat messages are valid transport layer messages that will be ignored by protocols at higher levels of a data communications stack. As an example, the techniques may send a TCP message containing only a carriage return and line feed (“CRLF”) in its payload. Because the TCP layer considers a message containing only a CRLF to be a valid TCP message, intermediary computing devices such as proxy servers may not interpret heartbeat messages as “keep alive” messages, and may sustain session connections.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: In an embodiment, techniques for sustaining session connections are provided. The techniques send heartbeat messages when not sending a message may cause the session connection to close because of a timeout condition. Heartbeat messages are valid transport layer messages that will be ignored by protocols at higher levels of a data communications stack. As an example, the techniques may send a TCP message containing only a carriage return and line feed (“CRLF”) in its payload. Because the TCP layer considers a message containing only a CRLF to be a valid TCP message, intermediary computing devices such as proxy servers may not interpret heartbeat messages as “keep alive” messages, and may sustain session connections.

Abstract: A system for conveniently extending the capabilities of network systems to support telephony is presented. Also, a method and system for preventing message looping within network devices that support telephony is presented. A network system, such as a proxy server, executes one or more executable service modules having instructions for performing a specific telephony service. A dispatcher operating upon the network device dispatches messages to the service modules according to a set of resource data provided by the service modules. To prevent message looping, the dispatcher executes logical instructions that restrict the service modules from routing messages to each other indefinitely.

Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

Abstract: In an embodiment, techniques for sustaining session connections are provided. The techniques send heartbeat messages when not sending a message may cause the session connection to close because of a timeout condition. Heartbeat messages are valid transport layer messages that will be ignored by protocols at higher levels of a data communications stack. As an example, the techniques may send a TCP message containing only a carriage return and line feed (“CRLF”) in its payload. Because the TCP layer considers a message containing only a CRLF to be a valid TCP message, intermediary computing devices such as proxy servers may not interpret heartbeat messages as “keep alive” messages, and may sustain session connections.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: In an embodiment, techniques for sustaining session connections are provided. The techniques send heartbeat messages when not sending a message may cause the session connection to close because of a timeout condition. Heartbeat messages are valid transport layer messages that will be ignored by protocols at higher levels of a data communications stack. As an example, the techniques may send a TCP message containing only a carriage return and line feed (“CRLF”) in its payload. Because the TCP layer considers a message containing only a CRLF to be a valid TCP message, intermediary computing devices such as proxy servers may not interpret heartbeat messages as “keep alive” messages, and may sustain session connections.

Abstract: Techniques to allow applications to propagate information to the other instances of the applications running on downstream servers are provided. An indicator, such as a token, tag, etc., is placed within or added to a message that is flowing through the distributed environment to signify that a process has been performed on the message. For example, when an instance of an application running on a server receives a message, the application instance can examine the indicator contained in the message and take appropriate action. If the application instance decides to process the message, the application instance can include an indicator in the message to signify that the application instance processed the message. The presence of the indicator signifies that the message has been processed by an upstream instance of the same application.

Abstract: In an embodiment, techniques for sustaining session connections are provided. The techniques send heartbeat messages when not sending a message may cause the session connection to close because of a timeout condition. Heartbeat messages are valid transport layer messages that will be ignored by protocols at higher levels of a data communications stack. As an example, the techniques may send a TCP message containing only a carriage return and line feed (“CRLF”) in its payload. Because the TCP layer considers a message containing only a CRLF to be a valid TCP message, intermediary computing devices such as proxy servers may not interpret heartbeat messages as “keep alive” messages, and may sustain session connections.

Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

Abstract: A system for conveniently extending the capabilities of network systems to support telephony is presented. Also, a method and system for preventing message looping within network devices that support telephony is presented. A network system, such as a proxy server, executes one or more executable service modules having instructions for performing a specific telephony service. A dispatcher operating upon the network device dispatches messages to the service modules according to a set of resource data provided by the service modules. To prevent message looping, the dispatcher executes logical instructions that restrict the service modules from routing messages to each other indefinitely.