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

Michael Jumper closed GUACAMOLE-4.
----------------------------------
    Resolution: Done

Completed prior to full migration to Apache infrastructure.

> Implement session recording
> ---------------------------
>
>                 Key: GUACAMOLE-4
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-4
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-server, RDP, SSH, Telnet, VNC
>            Reporter: Michael Jumper
>            Priority: Critical
>             Fix For: 0.9.10-incubating
>
>
> {panel:bgColor=#FFFFEE}
> *This description of this issue was copied from 
> [GUAC-236|https://glyptodon.org/jira/browse/GUAC-236], 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}
> -Once screen sharing work has been completed, Guacamole should have the 
> foundation necessary to support recording of a shared screen.-
> As originally stated in a [forum 
> post|http://sourceforge.net/p/guacamole/discussion/1110834/thread/d0e0516e/], 
> the only mechanism for this previously was to record raw Guacamole protocol 
> data:
> {quote}
> If you want to make a video of a Guacamole session, the best way would be to 
> record the Guacamole protocol between guacd and the web application (along 
> with timing information), and translate that into video.
> {quote}
> As mentioned in comments on this issue, mechanisms exist for recording VNC 
> directly as well, but as these will involve additional VNC connections (and 
> thus more bandwidth), handling the duplication of connections within guacd 
> would be more efficient. This is, in fact, one of the main driving forces 
> behind screen sharing at the Guacamole level.



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

Reply via email to