Thanks - what you say makes a great deal of sense. If I had total control of all elements of the system I'd do it like that. Unfortunately I may be stuck connecting over RDP to a single high resolution desktop that needs to be split to 4 browser clients, that much is out of my control So I guess I am stuck with all updates going to all browser clients.
Thanks for your patience! Neil On Tue, 4 May 2021 at 15:15, Craig Sawyer <[email protected]> wrote: > Neil, this is all correct as I understand it. Only changes are sent, > but if you only care about the changes in 1 corner, you will get it > all anyway. > > The right way to solve this is to just use 4 different displays. I.e. > You have 4 separate desktops showing whatever you care about, and then > the 4 clients you are showing this stuff to, will have 4 unique > connections, 1 to each of the 4 separate desktop connections in > Guacamole. > > You are trying to break how guacamole was designed to work, when the > "guac" solution is right in front of you, have 4 distinct connections, > to 4 distinct desktops, 1 per "quadrant" as you are saying. This way > you aren't trying to break how guac works, for no good reason. Just > have 1 app on 1 desktop display whatever is on quadrant 1, which > would be 1 desktop connection in guac and so on. > > IF you have some requirement, where you have some physical display > that needs to see all 4 on the same physical screen, that too is > easily accomplished with 4 browser windows, 1 per guac connection. It > will be basically just as efficient as what you are describing, but > with no actual code or work on your part. > > You don't need to invent anything new here, no new code or feature is > required. > > > On Tue, May 4, 2021 at 1:25 AM Neil Canham > <[email protected]> wrote: > > > > But those changes may be occurring in quadrants of the display that a > particular client has no interest in as they are not displaying them. I'm > really not trying to be deliberately difficult, but I'm clearly missing > something. Imagine clients 1-4 displaying quarters of the whole desktop. > Now imagine that the desktop has some realtime graphical display of > changing data so changes may be happening in all four quadrants > simultaneously. Client 1 will get the changing data for all quadrants, > despite only needing the changing data for their quadrant. Or maybe changes > are happening only in quadrant 2 but those changes get sent to client 1 > even though it doesn't need them - unless there is a way that the client > is indicating to the server which area it is displaying. It seems I must > have got this totally wrong somehow but I'm not sure how? > > > > On Mon, 3 May 2021 at 21:17, Mike Jumper <[email protected]> > wrote: > >> > >> On Sun, May 2, 2021 at 11:09 PM Neil Canham < > [email protected]> wrote: > >>> > >>> 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. > >> > >> > >> No. Only the changed portions of the screen will be sent. > >> > >> Michael Jumper > >> CEO, Lead Developer > >> Glyptodon Inc. > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
