Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How many sockets are opened between the browser and Kaazing Enterprise Gateway? And how many if cross-origin messaging is used?

April 26, 2017browser cross-origin Enterprise Gateway kaazing Messaging opened Sockets Used

0

Posted

How many sockets are opened between the browser and Kaazing Enterprise Gateway? And how many if cross-origin messaging is used?

1 Answer

0

Posted

Same-origin and cross-origin connection profiles are identical. One persistent connection is required from browser to Gateway. This will either be a full-duplex, bidirectional WebSocket connection, or a (possibly encrypted) HTTP downstream. In the second case, upstream traffic is sent on-demand over a second HTTP connection. Kaazing uses SSE on this second connection, so no polling is used at all. With cross-origin facilities, Kaazing software allows many sockets to be opened within the browser, each socket connecting to a different domain.