Furthermore, since Publisher cannot receive the data messages it sends, it may be easier to implement because Publisher does not have to discard the received data. When creating an application that wants to reflect user operations in the UI without delay, such as a whiteboard, it is better for the user experience to reflect them in the UI before sending data messages, so I think it will be similar regardless of whether Publisher can receive data messages or not. Drawing on the canvas of each SubscribersĪs mentioned earlier, Publisher cannot receive the data messages it sends, so it must draw on its own canvas before sending the data messages.Sending coordinates from Broker to each Subscriber.Send coordinates to Broker(Chime) as a data message (real-timeSendDataMessage).Detects mouse events/touch events on the Publisher’s browser’s canvas (HTMLCanvasEelemnt) and identifies the coordinates.Here’s the general process flow of the shared whiteboard we created. I think the advantage of the publish/subscribe model is that it allows publishers and subscribers to completely ignore each other’s relationships, so the fact that publishers can’t receive data when they’re in the same software (session) was just a little off. Note that this function may not be able to receive the data message even if the Publisher of the data message has subscribed to the topic of the data message, so you may need to be careful. We don’t know the details of the internal processing, especially the data flow, but it’s probably running on a general publish/subscribe model.Īfter using it this time, I found it to be a very easy to use feature. Then, when the sender sends a data message with Topic, the client receives the data message and calls the callback function corresponding to Topic. This function sends data messages with “Topic”.įirst of all, each client registers a callback function that defines the process for each Topic. The three new methods offered are as follows So developers can easily add things like shared whiteboards to their video conferencing systems without having to provide a server for messaging. The new feature leverages the managed communication path for this signaling to allow arbitrary data messages to be exchanged. If you want to know more about WebRTC and its relationship with signaling, please refer to this page.Īmazon Chime provides managed relay servers and signaling channels to make it easy to start video conferencing in a variety of network environments. The exchange of information about these routes is also done through signaling communication. Specifically, WebRTC is used for P2P communication between browsers, and the signaling communication is used to identify the destination of the other party or to exchange keys for cryptographic communication in order to start this communication.Īnd, even though it is called P2P communication, it is necessary to go through a relay server called TURN when communicating over a firewall. Amazon Chime’s video conferencing is achieved using a technology called WebRTC, and in WebRTC, signaling communication is used to control the session. This additional features of the Amazon Chime SDK uses the signaling communication already existing in Amazon Chime.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |