On Sat, Feb 29, 2020 at 6:17 AM Manoj Patil <[email protected]> wrote:
> Dear mike, > > We have captured the Guacamole screen recording as per your suggestions. > please find attachment and guide us what data is sent . > Looking through the recording, everything looks absolutely fine. All updates are incremental, and updates to large parts of the screen are only sent when those parts of the screen have indeed changed. This change is sometimes subtle (a window border changes color due to losing focus, drop shadow appears in front of something that otherwise hasn't changed, buttons become enabled/disabled, etc.), but the changes are there. The raw data is just over 5 MB and covers a session around 8 minutes in length. Average bandwidth usage over that timeframe would have been around 86 Kbps (10 KB/s), however that actually would have been closer to 57 Kbps (7 KB/s) with the additional gzip compression typically applied between Tomcat and the browser. There is no problem here. How we can see that file data? > You can manually walk through the data - the Guacamole protocol is text and is documented: http://guacamole.apache.org/doc/gug/guacamole-protocol.html http://guacamole.apache.org/doc/gug/protocol-reference.html You can also play back the recording in-browser and watch as parts of the recording are decoded. There's an example of this in the Guacamole source: https://github.com/apache/guacamole-client/tree/master/doc/guacamole-playback-example There's also a third-party hosted version of the above which I wrote for my day job that has some modifications to support loading larger files: https://player.glyptodon.com/ - Mike
