Alternative to joinme1/7/2024 Higher performance, as items, will be rendered on your screen instead of somewhere remotely.No loss of quality, as we do not need to apply compression to the content itself.It requires less bandwidth to synchronize state changes, so it will still work also very well on poor connections.The content will be drawn on your own computer + screen directly instead of somewhere remotely. Surfly’s HTML Sharing Protocol does not send over raw pixel data but rather sends the real HTML content and direct references to all sources that build up the page on the screen of the participant. Co-browsing – Surfly’s HTML Sharing Protocol Not only does this require CPU intensive encoding but it also reduces the image quality of the content. However, in most cases, the required bandwidth for sending these type of frames/images is still too high for most network connections so the image data is compressed. This helps reduce the required bandwidth for a simple operation such as scrolling up and down, as it can just reference the data from the previous frame and it no longer needs to send all the bits over the network. More intelligent approaches cut up each frame into multiple rectangles and then send updates not just as new data but also by reference to ‘older’ rectangles in a previous frame. This is, however, very bandwidth-intensive and requires a very good internet connection. In the most simple implementation, it just sends screenshot by screenshot (frame by frame) and raw pixel data. It looks at what is on the screen and sends that over the network to other participants. Screen sharing – Remote Framebuffer Protocol The Remote Framebuffer Protocol is used by most screen sharing solutions such as GoToMeeting, JoinME, Skype, Hangouts, Zoom and almost all other co-browsing solutions. The second approach is a different protocol that actually synchronizes the content and not so much the visual representation. If you inspect how these tools synchronize content from one part of the world to another, you can globally identify two different approaches. When comparing screen sharing solutions with a pure HTML based co-browsing solution, such as Surfly, there are lots of similarities but also a few key differences which become more clear when you look at the underlying technology.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |