Is it correct non-documented solution for Opentok react-native

Question

I faced an issue dealing with relocating video streams inside the grid.

For example, when we want to Pin 1 or 2 video streams to the top of the screen. That 1 or 2 video streams belong to users with specific role. I.E. that streams should always be at the top of the screen. But since this is multiple users session and on one device publisher has this specific role and on other device that role belongs to a subscriber we can’t pin that specific stream to the top using components layout from documentation.

We used undocumented approach, in detail - element OTPublisher is located inside the element OTSubscriber.

Although - based on documentation - the markup should be the following:

<OTSession {…sessionProps}>
   <OTPublisher {...publisherProps} />
   <OTSubscriber {...subscriberProps}>
       ...
       <StreamView {...streamProps} />
       ...
   </OTSubscriber>
</OTSession>

So stream for Publisher and streams for Subscriber work separately. It is a normal grid when we want to get visually consistent grid of streams.

As for our case, to control and manipulate with the grid we located OTPublisher inside of the group of elements for OTSubscriber. The markup finally turned out to be:

<OTSession {…sessionProps}>
   <OTSubscriber {...subscriberProps}>
       <OTPublisher {...publisherProps} />
       ...
       <StreamView {...streamProps} />
       ...
   </OTSubscriber>
</OTSession>

It seems like working at first glance, but OTSession communicates by itself with child elements and we might face side effects (including critical) by violating standard structure of elements location inside OTSession.

Seems like this solution might be potentially unstable. Could you please review our solution for stability? We want to minimise risk of this solution to be broken by future Vonage/TokBox updates. Would you please share any comments that can make our solution to Pin and control grid stable

question from:https://stackoverflow.com/questions/65885879/is-it-correct-non-documented-solution-for-opentok-react-native

Answer 1

Waitting for answers