larksr_websdk 3.3.113 → 3.3.114

package/dist/doc/en/multi_media_3_2_401.md

@@ -1,84 +1,84 @@
-# 3.2.401
-
-> The multimedia channel feature of version 3.2.401 is enabled on rendering server 3.2.2.0+.
-
-## New Features in 3.2.401
-
-> The following sample code assumes that the `larksr` object has been initialized and connected successfully.
-> Test demo: https://github.com/ParaverseTechnology/lark_sr_websdk_demos/tree/gh-pages
-
-(1). Added multi-channel media upload feature for the Web. Use `larksr.getMediaSharePeerConnection(index)` to get the media upload channel.
-
-The index supports 0 - 5. The media operations after obtaining the media channel are the same as the previous interface. The original interface is equivalent to `getMediaSharePeerConnection(0)`.
-
-Usage example:
-
-```javascript
-larksr.getMediaSharePeerConnection(0).openVideo();
-larksr.getMediaSharePeerConnection(0).closeVideo();
-```
-
-> When connecting to an older version of the rendering server that does not support multi-channel upload, only channel 0 will work.
-
-(2). Get the connection status of a specific channel using `getStats`
-
-```javascript
-larksr.getMediaSharePeerConnection(0).getStats()
-.then((res) => {
-    console.log("state: ", res);
-})
-.catch((e) => {
-    console.log("get state failed", e);
-})
-```
-
-(3). Set the video encoding for a specific connection channel using `preferVideoCode`
-
-```javascript
-larksr.getMediaSharePeerConnection(0).preferVideoCode = 'h264';
-```
-
-> If the current browser supports the specified video encoding, it will be used preferentially. If not, the default encoding method will be used.
-> The setting will take effect the next time the video is opened. The already opened video will not change.
-
-(4). Set the video upload bitrate for a specific connection channel
-
-```javascript
-larksr.getMediaSharePeerConnection(0).codeRate = {
-        start: 1000,
-        min: 1000,
-        max: 20000,
-}
-```
-
-> The setting will take effect the next time the video is opened. The already opened video will not change.
-
-(5). Media connection channels can listen to events separately, for example:
-
-```javascript
-larksr.getMediaSharePeerConnection(0).on("rtc_state_change", function(e) {
-    console.log("ice state change", e);
-});
-```
-
-(6). The opened or saved media channel object has a separate id, 0 - 5
-
-```javascript
-larksr.getMediaSharePeerConnection(0).id
-```
-
-(7). Force the use of canvas mode, the canvas of the video channel can rotate the screen clockwise or counterclockwise
-
-Enable rotation
-
-```javascript
-larksr.getMediaSharePeerConnection(0).forceRenderToCanvas = true;
-```
-
-Force clockwise rotation
-
-```javascript
-larksr.getMediaSharePeerConnection(0).canvasRender.setRotate(true);
-```
-
+# 3.2.401
+
+> The multimedia channel feature of version 3.2.401 is enabled on rendering server 3.2.2.0+.
+
+## New Features in 3.2.401
+
+> The following sample code assumes that the `larksr` object has been initialized and connected successfully.
+> Test demo: https://github.com/ParaverseTechnology/lark_sr_websdk_demos/tree/gh-pages
+
+(1). Added multi-channel media upload feature for the Web. Use `larksr.getMediaSharePeerConnection(index)` to get the media upload channel.
+
+The index supports 0 - 5. The media operations after obtaining the media channel are the same as the previous interface. The original interface is equivalent to `getMediaSharePeerConnection(0)`.
+
+Usage example:
+
+```javascript
+larksr.getMediaSharePeerConnection(0).openVideo();
+larksr.getMediaSharePeerConnection(0).closeVideo();
+```
+
+> When connecting to an older version of the rendering server that does not support multi-channel upload, only channel 0 will work.
+
+(2). Get the connection status of a specific channel using `getStats`
+
+```javascript
+larksr.getMediaSharePeerConnection(0).getStats()
+.then((res) => {
+    console.log("state: ", res);
+})
+.catch((e) => {
+    console.log("get state failed", e);
+})
+```
+
+(3). Set the video encoding for a specific connection channel using `preferVideoCode`
+
+```javascript
+larksr.getMediaSharePeerConnection(0).preferVideoCode = 'h264';
+```
+
+> If the current browser supports the specified video encoding, it will be used preferentially. If not, the default encoding method will be used.
+> The setting will take effect the next time the video is opened. The already opened video will not change.
+
+(4). Set the video upload bitrate for a specific connection channel
+
+```javascript
+larksr.getMediaSharePeerConnection(0).codeRate = {
+        start: 1000,
+        min: 1000,
+        max: 20000,
+}
+```
+
+> The setting will take effect the next time the video is opened. The already opened video will not change.
+
+(5). Media connection channels can listen to events separately, for example:
+
+```javascript
+larksr.getMediaSharePeerConnection(0).on("rtc_state_change", function(e) {
+    console.log("ice state change", e);
+});
+```
+
+(6). The opened or saved media channel object has a separate id, 0 - 5
+
+```javascript
+larksr.getMediaSharePeerConnection(0).id
+```
+
+(7). Force the use of canvas mode, the canvas of the video channel can rotate the screen clockwise or counterclockwise
+
+Enable rotation
+
+```javascript
+larksr.getMediaSharePeerConnection(0).forceRenderToCanvas = true;
+```
+
+Force clockwise rotation
+
+```javascript
+larksr.getMediaSharePeerConnection(0).canvasRender.setRotate(true);
+```
+
 > The setting will take effect the next time the video is opened. The already opened video will not change.

package/dist/doc/en/sdkid_encryption.md

@@ -1,40 +1,40 @@
-# SDK ID Encryption Configuration
-
-To use the larksr SDK, you first need to obtain an SDK authorization code from Pingxingyun Business (business@pingxingyun.com) or at https://www.pingxingyun.com/console (note that this is not the server-side authorization code).
-
-Pass the `authCode` through larksr config or set the authorization code using the method `larksr.initSDKAuthCode('YourSDKID')`.
-
-To protect the security of the SDK ID, from server version 3.2.3.0 onwards, you can configure SDK ID encryption.
-
-Configure SDK encryption:
-
-1. First, log in to the larkxr platform backend, find System Settings -> Access Management -> SDKID Key Management to generate an SDK ID encryption key.
-
-2. Encrypt the SDK ID
-
-The following is an example in Java:
-
-```java
-public static void main(String[] args) {
-    /**
-    * @param res   The original string to be encrypted
-    * @param key   16-character key for encryption
-    */
-    try {
-        String res = "The original string to be encrypted";
-        String key = "16-character key for encryption";
-        String ALGORITHM = "AES";
-        String CHARSET = "UTF-8";
-        SecretKeySpec sks = new SecretKeySpec(key.getBytes(CHARSET), ALGORITHM);
-        Cipher cipher = Cipher.getInstance(ALGORITHM);
-        cipher.init(cipher.ENCRYPT_MODE, sks);
-        byte[] result = cipher.doFinal(res.getBytes());
-        // BASE64Encoder encoder = new BASE64Encoder();      //java8
-        Base64.Encoder encoder = Base64.getEncoder(); //java9+
-        System.out.println(encoder.encodeToString(result));
-    } catch (Exception e) {
-    }
-}
-```
-
-3. Pass the encrypted string into the lark configuration.
+# SDK ID Encryption Configuration
+
+To use the larksr SDK, you first need to obtain an SDK authorization code from Pingxingyun Business (business@pingxingyun.com) or at https://www.pingxingyun.com/console (note that this is not the server-side authorization code).
+
+Pass the `authCode` through larksr config or set the authorization code using the method `larksr.initSDKAuthCode('YourSDKID')`.
+
+To protect the security of the SDK ID, from server version 3.2.3.0 onwards, you can configure SDK ID encryption.
+
+Configure SDK encryption:
+
+1. First, log in to the larkxr platform backend, find System Settings -> Access Management -> SDKID Key Management to generate an SDK ID encryption key.
+
+2. Encrypt the SDK ID
+
+The following is an example in Java:
+
+```java
+public static void main(String[] args) {
+    /**
+    * @param res   The original string to be encrypted
+    * @param key   16-character key for encryption
+    */
+    try {
+        String res = "The original string to be encrypted";
+        String key = "16-character key for encryption";
+        String ALGORITHM = "AES";
+        String CHARSET = "UTF-8";
+        SecretKeySpec sks = new SecretKeySpec(key.getBytes(CHARSET), ALGORITHM);
+        Cipher cipher = Cipher.getInstance(ALGORITHM);
+        cipher.init(cipher.ENCRYPT_MODE, sks);
+        byte[] result = cipher.doFinal(res.getBytes());
+        // BASE64Encoder encoder = new BASE64Encoder();      //java8
+        Base64.Encoder encoder = Base64.getEncoder(); //java9+
+        System.out.println(encoder.encodeToString(result));
+    } catch (Exception e) {
+    }
+}
+```
+
+3. Pass the encrypted string into the lark configuration.