On Mon, Apr 24, 2023 at 2:14 AM Mike Brown <[email protected]> wrote: > > Hi all, > > I’m playing with the Xorg experimental driver and omg it’s so snappy and > beautiful. I understand that the driver implements it’s own guacd, and so the > recommendation (requirement?) is to configure a connection with type “xorg” > and the the target host and driver guacd port in the connection’s proxy > settings. > > All of that works, and if I configure connection parameters to enable > recording, I see the target gets them and tries to start recording. Except > that highlights our issue - we don’t want the target to be doing the > recording, or to even have access to that storage. We’d prefer an > intermediary guacd that can do the recording. I’m hoping this is one of them > dumb questions and I’m overlooking something obvious, but is there a way to > achieve this?
No, it's not a dumb question, and is sort of a product of how the Xorg driver has been written - that is, it is a complete replacement for guacd, rather than a protocol that guacd connects to. So, when you configure Guacamole client for that Xorg connection, and configure the guacd proxy to point to the Xorg system, you're completely bypassing the system running guacd that the other connections go to. It's almost as if we need to implement some sort of guacd "passthrough" support for this, where Guacamole can still be the ultimate protocol, but still pass it through guacd. I'll be interested to hear what others have to say about this - particularly Mike, since he's the one who implemented that support. > > I also wanted to say thank you for all of the effort and contributions that > make Guacamole a joy to use and engineer with. It’s been so much fun figuring > out how to make it work how we want. Thanks for the kind words - it's a lot of fun to contribute to it, and has a great community. Thanks for being part of it. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
