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

Michael Jumper resolved GUACAMOLE-13.
-------------------------------------
    Resolution: Done

Completed prior to full migration to Apache infrastructure.

> Finally stabilize and merge GUAC-844 to master
> ----------------------------------------------
>
>                 Key: GUACAMOLE-13
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-13
>             Project: Guacamole
>          Issue Type: Task
>          Components: guacd, libguac, RDP, SSH
>            Reporter: Michael Jumper
>            Priority: Blocker
>             Fix For: 0.9.10-incubating
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from 
> [GUAC-1389|https://glyptodon.org/jira/browse/GUAC-1389], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> It has been far too long since the code for 
> [GUAC-844|https://glyptodon.org/jira/browse/GUAC-844] was completed at an API 
> level, and far too long since any work was done to bring master and the 
> [GUAC-844|https://glyptodon.org/jira/browse/GUAC-844] branch in line with 
> each other. We need to merge things together and ditch the 
> [GUAC-844|https://glyptodon.org/jira/browse/GUAC-844] branch before it 
> diverges so far that merging is pointless.
> This issue will solve what 
> [GUAC-826|https://glyptodon.org/jira/browse/GUAC-826], 
> [GUAC-827|https://glyptodon.org/jira/browse/GUAC-827], 
> [GUAC-845|https://glyptodon.org/jira/browse/GUAC-845], and 
> [GUAC-846|https://glyptodon.org/jira/browse/GUAC-846] were intended to solve, 
> but with in one not-so-swift sprint-worth of a stroke.
> Note that, for the sake of compatibility and getting things actually merged, 
> and for the sake of streaming making sense, all streams without an obvious 
> destination (printing, for example) should be sent only to the owner of the 
> connection (the root of the sharing tree for a given connection). Eventually, 
> audio should be broadcast to all users, but it is fine for audio to be sent 
> only to the owner initially.



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

Reply via email to