[
https://issues.apache.org/jira/browse/GUACAMOLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper resolved GUACAMOLE-189.
--------------------------------------
Resolution: Done
> Add support for per-connection guacd
> ------------------------------------
>
> Key: GUACAMOLE-189
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-189
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole, guacamole-ext
> Reporter: Michael Jumper
> Assignee: Michael Jumper
> Fix For: 0.9.13-incubating
>
>
> The web application currently assumes that one guacd will be used to provide
> access to all connections. This assumption fails if:
> * Multiple guacd instances are spread out across different networks
> * Another component implementing the Guacamole protocol is being used instead
> of guacd on a per-connection basis (like the X.Org driver of GUACAMOLE-168)
> Though no change is needed to the core APIs, as no such assumption is made at
> that level, the web application and extension API should be modified such
> that the guacd (or other Guacamole proxy) applicable to a connection can be
> specified explicitly for that connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
