On 1/25/2020 4:25 PM, Mike Jumper wrote:
On Wed, Jan 22, 2020 at 2:47 PM Support <[email protected]
<mailto:[email protected]>> wrote:
...
I'm still confused about the place of guacamole-server, does it
manage the bridge between the clients and the server service like
vnc server or remoteApp?
Not exactly. It is not a bridge between the clients and remote desktop
services as the clients do not actually connect to guacd (the service
component of guacamole-server). The guacd service functions purely as
an internal workhorse for the web application. The union of the entire
Guacamole deployment could be considered a bridge like you describe,
but not guacd on its own.
guacd and the other parts of guacamole-server form a protocol-agnostic
remote desktop proxy and optimizer. From the perspective of the web
application, guacd functions as an abstraction layer which allows the
JavaScript client served by the web application to narrow its scope to
just one protocol: the Guacamole protocol.
This separation means that:
* guacamole-client doesn't need to worry about low-level protocol
specifics
* guacamole-server doesn't need to worry about high-level
authentication and authorization specifics
* guacamole-server can take advantage of native libraries which make
it easier to support the various protocols
See:
http://guacamole.apache.org/doc/gug/guacamole-architecture.html
- Mike
it's more clear now, thanks Mike!
David
--
E-BLOKOS
