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 2018/10/30 03:08:00 UTC

[jira] [Commented] (GUACAMOLE-597) Allow fine-grained control of terminal output redirection via pipe streams

    [ https://issues.apache.org/jira/browse/GUACAMOLE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668062#comment-16668062 ] 

Michael Jumper commented on GUACAMOLE-597:
------------------------------------------

It _would_ be minor enough, for sure, but since there are already changes warranting a full bump to 2.0.0 on master, everything else on master goes with it.

If it's possible to rearrange release/branching procedures to allow non-breaking changes to be released in a patch release, that may be worth doing in the future. Not sure what that would be, though it would presumably involve a number of active development branches (multiple staging branches), each dedicated to an upcoming release.

> Allow fine-grained control of terminal output redirection via pipe streams
> --------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-597
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-597
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: Terminal
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>
> While Guacamole's terminal emulator allows output to be redirected to a pipe stream for the benefit of client-side JavaScript (see GUACAMOLE-17), doing so currently has caveats:
> * Redirecting output to a pipe stream results in _all_ output going solely to that stream. No output is displayed on the terminal while the pipe stream remains open. This is not always desirable.
> * Data sent to the pipe stream is buffered. This works well for non-interactive bulk transfers of data, but any client-side JavaScript expecting to monitor output in real-time will be disappointed, particularly code which must deal with the output of interactive commands.
> There should be some option to allow output to go to both the pipe stream and the terminal, and some option to allow the output to be automatically flushed, whether that be through a new OSC code or through backward-compatible modifications to the existing code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)