Hi Mike Thanks for clarifying how Guacamole is working. Am I right in thinking though that if there were changes occurring in all four quadrants of the original desktop, without some kind of server-side mechanism to select only a given quadrant per client, lots of unnecessary data would be delivered to all clients? That is what I'd live to avoid.
Neil On Fri, 30 Apr 2021 at 21:35, Mike Jumper <[email protected]> wrote: > On Fri, Apr 30, 2021 at 6:54 AM Neil Canham < > [email protected]> wrote: > >> Hi >> I have a requirement to connect over RDP to a high resolution desktop, >> and return that desktop as 4 separate parts (quadrants) to 4 different >> browser clients. Is this something I could do with Guacamole? I have some >> experience in building custom browser UI (Javascript and Servlet) for >> Guacamole. What I'm keen to avoid is returning the entire high resolution >> screen to each client and only rendering a portion - that would seem >> inefficient if there is a way to do the split in the Guacamole server. >> > > This does not happen and would indeed be inefficient. After initializing > the display, the only graphical data sent from server to client will be the > parts of the screen that have changed. You don't need to try to manually > split anything - sending only the required changes is what Guacamole > already does by design. > > Michael Jumper > CEO, Lead Developer > Glyptodon Inc <https://glyp.to/>. > >
