WebSocket connection lost when recover with cached token

[ruleechen]

The feature of recover from cached token works well for single page. When we open two or more pages, each page try to recover from the cached token. The pages will try to launch their own websocket connection.

Then it comes to this issue:

Each page will call the below api, but calling this api will disconnect other pages worksocket connection as my test.

ringcentral-extensible/packages/extensions/ws/index.ts

Line 245 in 76ae3d7

const r = await this.rc.post('/restapi/oauth/wstoken');

[tylerlong]

The root cause is: one wsToken can only establish one connection. If multiple tabs/pages share the same cached wsToken, existing connections will be disconnected upon new connections created.