Customer Support

How can we help you today?

Using a different/modified version of AdapterJS with Skylink

Modified on: Fri, 22 Dec, 2017 at 4:33 PM

Loading a custom version of AdapterJS is useful when you want to work with a different/modified version of AdapterJS. Modification is also required when you want to build a custom version of the screen-sharing extensions to use on your domains.

1. Linking to socket.io-client

To ensure that SkylinkJS works as expected with socket and peer connections, we recommended that you link to the corresponding version of socket.io that the version of SkylinkJS you are using has. The release notes will contain the version of socket.io-client each SkylinkJS release uses.

You can point to the socket.io CDN, as shown below. Simply replace << >> in the below snippet with the version you are intending to use.

Alternatively, if you would prefer hosting this on your end, we would recommended downloading socket.io-client from here. The file name is socket.io.js in the release zip.

2. Linking to customised AdapterJS

To ensure that SkylinkJS works as expected and is updated with the correct WebRTC interface polyfills, we recommend that you link to the corresponding version of AdapterJS that the SkylinkJS version you are using, has. The release notes will contain the version of AdapterJS each SkylinkJS release uses.

You can point to the Temasys CDN if do not intend to make any modifications to AdapterJS. Simply replace << >> in the code-snippet shown below, with the version you would like to use.

You may use the compressed and production version of SkylinkJS with skylink.min.js.

Why not use skylink.complete.js?Bundled versions of SkylinkJS, contain a fixed version of AdapterJS and socket.io-client. So, you will not be able to modify the AdapterJS to use your customised version