[
https://issues.apache.org/jira/browse/GUACAMOLE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963706#comment-15963706
]
Michael Jumper commented on GUACAMOLE-250:
------------------------------------------
When building the array of syncs (during processing of the received video),
could represent each sync as a "frame" object, with that frame either being
incremental (a set of instructions between itself and the previous frame) or
absolute (a snapshot of client state).
The would allow the transport receiving instructions to be abstracted away (no
need to use byte offsets, nor any need to maintain the original XHR as a
buffer), such that any tunnel implementation could be used as a source of
instructions. Besides being cleaner and easier to implement, this would allow
things like client-side session recording (or even DVR-like rewinding of an
active session) to be done using the same core pieces.
> Implement support for in-browser playback of screen recordings
> --------------------------------------------------------------
>
> Key: GUACAMOLE-250
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-250
> Project: Guacamole
> Issue Type: New Feature
> Reporter: yalinliu
> Assignee: Michael Jumper
> Priority: Minor
>
> Screen recordings of Guacamole sessions are simply dumps of the Guacamole
> protocol data from one side of the connection. Currently, these recordings
> are played back after being converted to video using {{guacenc}}, but they
> could just as easily be played back directly by Guacamole itself. Direct
> playback would remove the need to translate recordings to video (an expensive
> operation) and would allow playback within any browser which Guacamole
> already supports.
> Since the {{Guacamole.Client}} object accepts any implementation of the
> {{Guacamole.Tunnel}} interface, implementing some sort of "playback tunnel"
> which would parse Guacamole protocol from a static file (rather than connect
> through a Guacamole server tunnel) might be easy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
