Abstract: The present invention provides a method, system, and computer program product for facilitating end-user access to remote applications based on TCP (Transmission Control Protocol). TCP traffic is packaged into the body of HTTP (HyperText Transfer Protocol) messages, enabling the TCP traffic to be transmitted through HTTP systems in an application-independent manner as if it were native HTTP traffic. TCP traffic therefore flows through firewall systems without requiring access to an external TCP port, and flows through HTTP proxy servers as well. The disclosed technique enables mapping bi-directional TCP messages to HTTP, which is designed for client-initiated message traffic only.

Abstract: The present invention provides a method, system, and computer program product for facilitating end-user access to remote applications based on TCP (Transmission Control Protocol). TCP traffic is packaged into the body of HTTP (HyperText Transfer Protocol) messages, enabling the TCP traffic to be transmitted through HTTP systems in an application-independent manner as if it were native HTTP traffic. TCP traffic therefore flows through firewall systems without requiring access to an external TCP port, and flows through HTTP proxy servers as well. The disclosed technique enables mapping bi-directional TCP messages to HTTP, which is designed for client-initiated message traffic only.

Abstract: The present invention provides a method, system, and computer program product for facilitating end-user access to remote applications based on TCP (Transmission Control Protocol). TCP traffic is packaged into the body of HTTP (HyperText Transfer Protocol) messages, enabling the TCP traffic to be transmitted through HTTP systems in an application-independent manner as if it were native HTTP traffic. TCP traffic therefore flows through firewall systems without requiring access to an external TCP port, and flows through HTTP proxy servers as well. The disclosed technique enables mapping bi-directional TCP messages to HTTP, which is designed for client-initiated message traffic only.

Abstract: Software components such as objects, applications and computational blocks are linked through a data flow manager and an interface that facilitate data exchange between the components. The interface defines a communication protocol. Components that comply with the protocol can share data, even if such components are associated with unrelated applications. Non-compliant components can be paired with translation objects or controlled by scripts to allow such non-compliant components to be linked to compliant components for data sharing. The data flow manager controls data exchange by determining which components are prepared to share data, and then prompting only prepared components to share data. Data exchange is executed in discrete steps.