From b58250b64f3e9efa2b50224fde6ce276573f5e6d Mon Sep 17 00:00:00 2001
From: pabloFuente <pablofuenteperez@gmail.com>
Date: Wed, 1 Jul 2020 17:38:01 +0200
Subject: [PATCH] OpenVidu SDKs COMPOSED_QUICK_START doc description

---
 .../io/openvidu/java/client/Recording.java    | 23 ++++++++++++++++---
 openvidu-node-client/src/Recording.ts         | 20 ++++++++++++----
 2 files changed, 36 insertions(+), 7 deletions(-)

diff --git a/openvidu-java-client/src/main/java/io/openvidu/java/client/Recording.java b/openvidu-java-client/src/main/java/io/openvidu/java/client/Recording.java
index 455759b4..84f8500f 100644
--- a/openvidu-java-client/src/main/java/io/openvidu/java/client/Recording.java
+++ b/openvidu-java-client/src/main/java/io/openvidu/java/client/Recording.java
@@ -77,9 +77,26 @@ public class Recording {
 		INDIVIDUAL,
 		
 		/**
-		 * EXPERIMENTAL
-		 * This option is intended to keep a recorder session openned for
-		 * incoming recording requests to be recorded as fast as possible
+		 * Works the same way as COMPOSED mode, but the necessary recorder
+		 * service module will start some time in advance and won't be terminated
+		 * once a specific session recording has ended. This module will remain
+		 * up and running as long as the session remains active.<br><br>
+		 * 
+		 * <ul>
+		 * <li>
+		 * <strong>Pros vs COMPOSED</strong>: the process of starting the recording will be noticeably
+		 * faster. This can be very useful in use cases where a session needs to be
+		 * recorded multiple times over time, when a better response time is usually
+		 * desirable.
+		 * </li>
+		 * <li>
+		 * <strong>Cons vs COMPOSED</strong>: for every session initialized with COMPOSED_QUICK_START
+		 * recording output mode, extra CPU power will be required in OpenVidu Server.
+		 * The recording module will be continuously rendering all of the streams being
+		 * published to the session even when the session is not being recorded. And that
+		 * is for every session configured with COMPOSED_QUICK_START.
+		 * </li>
+		 * </ul>
 		 */
 		COMPOSED_QUICK_START;
 	}
diff --git a/openvidu-node-client/src/Recording.ts b/openvidu-node-client/src/Recording.ts
index d7e3acb0..85635e3a 100644
--- a/openvidu-node-client/src/Recording.ts
+++ b/openvidu-node-client/src/Recording.ts
@@ -142,10 +142,22 @@ export namespace Recording {
          */
         COMPOSED = 'COMPOSED',
         
-        /**
-		 * EXPERIMENTAL
-		 * This option is intended to keep a recorder session openned for
-		 * incoming recording requests to be recorded as fast as possible
+		/**
+		 * Works the same way as COMPOSED mode, but the necessary recorder
+		 * service module will start some time in advance and won't be terminated
+		 * once a specific session recording has ended. This module will remain
+		 * up and running as long as the session remains active.
+		 * 
+		 * - **Pros vs COMPOSED**: the process of starting the recording will be noticeably
+		 * faster. This can be very useful in use cases where a session needs to be
+		 * recorded multiple times over time, when a better response time is usually
+		 * desirable.
+
+		 * - **Cons vs COMPOSED**: for every session initialized with COMPOSED_QUICK_START
+		 * recording output mode, extra CPU power will be required in OpenVidu Server.
+		 * The recording module will be continuously rendering all of the streams being
+		 * published to the session even when the session is not being recorded. And that
+		 * is for every session configured with COMPOSED_QUICK_START.
 		 */
         COMPOSED_QUICK_START = 'COMPOSED_QUICK_START',