Added the ability to use the Kaazing WebSocket client library without overriding the browser's native WebSocket object (kaazing.io/1605)

This change is backward compatible. That is the window.WebSocket object will continue to be overridden with the Kaazing implementation.

To prevent that, use the new WebSocket.noredefine.js library instead. For example:

<script type="text/javascript" language="javascript" src="WebSocket.noredefine.js"></script>

When using WebSocket.noredefine.js, other libraries or generic Javascript code that runs new WebSocket(...) will use the browser native window.WebSocket object, without any Kaazing modifications.

Other Kaazing client libraries, such as JmsClient.js, will work correctly irrespective of whether you use WebSocket.js or WebSocket.noredefine.js.

If you use WebSocket.noredefine.js, and would like to create a WebSocket connection that utilizes the Kaazing implementation – for it's extensions like inactivity.timeout or the ChallengeHandler - then you can create a new connection using the WebSocketEx object (for extended WebSocket):

const ws = new WebSocketEx("...");

JavaScript client is now available using npm (roadmap/388) Learn more

JavaScript client is now available using Bower (roadmap/388) Learn more

JavaScript client can be included in your application directly from CDN (roadmap/388) Learn more