Enterprise client-server system and methods of providing web application support through distributed emulation of websocket communications
A system enabling service communications in distributed Web applications between servers otherwise inaccessible due to cross-origin security restrictions in pre-HTML5 compliant Web-browser clients. A Web-browser client executes a client-side Web application received from a source origin server having a defined source origin and requests connections to request identified Web-application services. Execution of an emulation client library establishes a bidirectional capable HTTP-based communications connection between the Web-browser client and a gateway server, having a target origin outside the scope of the source origin, providing access to the request identified Web-application service. The bidirectional capable HTTP-based communications connection includes a cross-origin communications bridge providing a secure communications path between the source and target origins. The gateway server can establish an HTML5 compliant connection to a target defined service, provided by a target server, having a predefined relation to the request identified Web-application service.
1. A system for providing a bi-directional full-duplex connection, comprising;
a communication interface configured to
receive at a gateway server from a network client, a request to establish a bi-directional full-duplex network connection, wherein the request conforms to a half-duplex network connection protocol, wherein the half-duplex connection protocol is a HTTP based protocol; and
a processor coupled with the communication interface and configured to
process the request to determine a decision on whether to allow the bi-directional full-duplex connection,
in the event the decision is to allow the bi-directional full-duplex connection, establish the bi-directional full-duplex network connection using the half-duplex network connection protocol, wherein the bi-directional full-duplex connection utilizes a Web Socket communication protocol and establishing the bi-directional full-duplex connection utilizes a plurality of half-duplex connections,
provide a confirmation that the bi-directional full-duplex network connection has been established, and
allow communication between the network client and a target server via the gateway server and the established bi-directional full-duplex network connection.
2. The system of claim 1 , wherein the bi-directional full-duplex connection provides a real-time communication channel.
3. The system of claim 1 , wherein the bi-directional full-duplex connection is based at least in part on TCP.
4. The system of claim 1 , wherein the system is included in a gateway server.
5. The system of claim 1 , wherein the request includes configuration information of the bi-directional full-duplex connection.
6. The system of claim 5 , wherein the configuration information is associated with an access policy.
7. The system of claim 5 , wherein the configuration information includes a source origin identifier.
8. The system of claim 5 , wherein the configuration information includes a target origin identifier.
9. The system of claim 5 , wherein the configuration information includes a requested service identifier.
10. The system of claim 1 , wherein the processor is configured to evaluate a service access policy associated with the request.
11. The system of claim 1 , wherein the confirmation identifies that the request has been accepted.
12. The system of claim 1 , wherein the request is received from a client.
13. The system of claim 1 , wherein the request is received from a web-browser.
14. The system of claim 1 , wherein the bi-directional full-duplex connection enables cross-origin communication.
15. A method for providing a bi-directional full-duplex connection, comprising:
using a communication interface to receive at a gateway server from a network client, a request to establish a bi-directional full-duplex network connection, wherein the request conforms to a half-duplex network connection protocol, wherein the half-duplex connection protocol is a HTTP based protocol;
processing the request to determine a decision on whether to allow the bi-directional full-duplex connection;
in the event the decision is to allow the bi-directional full-duplex connection, establishing the bi-directional full-duplex network connection using the half-duplex network connection protocol, wherein the bi-directional full-duplex connection utilizes a Web Socket communication protocol and establishing the bi-directional full-duplex connection utilizes a plurality of half-duplex connections;
providing a confirmation that the bi-directional full-duplex network connection has been established; and
allowing communication between the network client and a target server via the gateway server and the established bi-directional full-duplex network connection.
16. A computer program product for providing a bi-directional full-duplex connection, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving at a gateway server from a network client, a request to establish a bi-directional full-duplex network connection, wherein the request conforms to a half-duplex network connection protocol, wherein the half-duplex connection protocol is a HTTP based protocol;
processing the request to determine a decision on whether to allow the bi-directional full-duplex connection;
in the event the decision is to allow the bi-directional full-duplex connection, establishing the bi-directional full-duplex network connection using the half-duplex network connection protocol, wherein the bi-directional full-duplex connection utilizes a Web Socket communication protocol and establishing the bi-directional full-duplex connection utilizes a plurality of half-duplex connections;
providing a confirmation that the bi-directional full-duplex network connection has been established; and
allowing communication between the network client and a target server via the gateway server and the established bi-directional full-duplex network connection.
17. The method of claim 15 , wherein the bi-directional full-duplex connection is based at least in part on TCP.
18. The method of claim 15 , wherein the system is included in a gateway server.
19. The method of claim 15 , wherein the request includes configuration information of the bi-directional full-duplex connection.
20. The method of claim 15 , wherein the bi-directional full-duplex connection enables cross-origin communication.