Add serverside livestreaming docs#115
Conversation
| </TabItem> | ||
| </Tabs> | ||
|
|
||
| Now, you can connect peer normally to the room as described in our [React Native](/react-native/connecting) and [React](/react/connecting) docs. |
There was a problem hiding this comment.
nitpick (blocking):
| Now, you can connect peer normally to the room as described in our [React Native](/react-native/connecting) and [React](/react/connecting) docs. | |
| Now, you can connect the peer normally to the room as described in our [React Native](/react-native/connecting) and [React](/react/connecting) docs. |
| </TabItem> | ||
| </Tabs> | ||
|
|
||
| Now you can connect viewer to the livestream as described in our [React Native] and [React] docs. |
There was a problem hiding this comment.
nitpick (blocking):
| Now you can connect viewer to the livestream as described in our [React Native] and [React] docs. | |
| Now you can connect the viewer to the livestream as described in our [React Native] and [React] docs. |
| Now you can connect viewer to the livestream as described in our [React Native] and [React] docs. | ||
|
|
||
| :::info | ||
| Viewers connect using [WHEP](https://blog.swmansion.com/introducing-react-native-whip-whep-ac9e5588d4da) standard, allowing the use of any player that supports the WHEP standard. |
There was a problem hiding this comment.
suggestion (blocking): I would link to something different here, and specify that there is React Native whip/whep for the mobile ecosystem.
There was a problem hiding this comment.
something different... like RFC?
There was a problem hiding this comment.
something like our article would be the best, but it's yet to be created :p
There was a problem hiding this comment.
imo lets not waste time here and approach this incrementally
| <TabItem value="ts" label="Typescript"> | ||
|
|
||
| ```ts | ||
| // createdRoom ... previously created room |
There was a problem hiding this comment.
issue (blocking): I would include the required part of the previous snippet with createdRoom init.
There was a problem hiding this comment.
It could suggest that you can do it twice, create one room for peer and another for viewer. What do you think?
|
|
||
| ### Viewers | ||
|
|
||
| To view the streamed content you need to obtain viewer token that can be generated using [Server SDKs](/production/server). |
There was a problem hiding this comment.
nitpick (blocking):
| To view the streamed content you need to obtain viewer token that can be generated using [Server SDKs](/production/server). | |
| To view the streamed content you need to obtain a viewer token that can be generated using [Server SDKs](/production/server). |
| - Compatible with WHEP standard | ||
| <!-- * TODO: compatibility with WHIP --> | ||
|
|
||
| ## How Do I Use It? |
There was a problem hiding this comment.
nitpick (blocking):
| ## How Do I Use It? | |
| ## How do I use it? |
| Main differences: | ||
|
|
||
| - Livestream rooms are 20% cheaper than regular rooms | ||
| - Livestream rooms allows for greater scalability |
There was a problem hiding this comment.
nitpick (blocking):
| - Livestream rooms allows for greater scalability | |
| - Livestream rooms allow for greater scalability |
|
|
||
| # Live streaming | ||
|
|
||
| For live streaming purposes we suggest using livestream rooms specifically optimized for this use case. |
There was a problem hiding this comment.
nitpick (blocking):
| For live streaming purposes we suggest using livestream rooms specifically optimized for this use case. | |
| For livestreaming purposes, we suggest using livestream rooms specifically optimized for this use case. |
There was a problem hiding this comment.
I think it's correct
|
|
||
| ### Streamer | ||
|
|
||
| To create a livestream room, you must set the `roomType` field to `broadcaster` when creating a room using our [Server SDKs](/production/server). Then you have to create one peer that will be used to stream your content. |
There was a problem hiding this comment.
nitpick (blocking):
| To create a livestream room, you must set the `roomType` field to `broadcaster` when creating a room using our [Server SDKs](/production/server). Then you have to create one peer that will be used to stream your content. | |
| To create a livestream room, you must set the `roomType` field to `broadcaster` when creating a room using our [Server SDKs](/production/server). Then you have to create a peer that will be used to stream your content. |
|
|
||
| ### Viewers | ||
|
|
||
| To view the streamed content you need to obtain viewer token that can be generated using [Server SDKs](/production/server). |
There was a problem hiding this comment.
nitpick (blocking):
| To view the streamed content you need to obtain viewer token that can be generated using [Server SDKs](/production/server). | |
| To view the streamed content, you need to obtain viewer token that can be generated using [Server SDKs](/production/server). |
f985045 to
239d2c6
Compare
19aaa5e to
e0de89e
Compare
| Now you can connect viewer to the livestream as described in our [React Native] and [React] docs. | ||
|
|
||
| :::info | ||
| Viewers connect using [WHEP](https://blog.swmansion.com/introducing-react-native-whip-whep-ac9e5588d4da) standard, allowing the use of any player that supports the WHEP standard. |
There was a problem hiding this comment.
imo lets not waste time here and approach this incrementally
Description
Closes FCE-1488
Adds server-side livestreaming documentation.
Things worth doing before merging this PR:
createBroadcastViewerTokentocreateLivestreamViewerTokeninjs-server-sdk