You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/01/25 00:41:26 UTC

[jira] [Resolved] (GUACAMOLE-175) Move core of guacd into utility library

     [ https://issues.apache.org/jira/browse/GUACAMOLE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper resolved GUACAMOLE-175.
--------------------------------------
       Resolution: Done
    Fix Version/s: 0.9.12-incubating

> Move core of guacd into utility library
> ---------------------------------------
>
>                 Key: GUACAMOLE-175
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-175
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-server, guacd
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.12-incubating
>
>
> Implementing a driver supporting the Guacamole protocol (like the X.Org driver being implemented for GUACAMOLE-168) requires essentially reimplementing guacd. To avoid this, we should move the core parts of guacd into a sane API, exposed as a utility library within guacamole-server.
> Eventually, it may make sense to make that API a public library installed by guacamole-server, but for now we can at least separate things for internal convenience.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)