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/05/27 21:58:00 UTC

[jira] [Assigned] (GUACAMOLE-567) Network connection problem acknowledgement/feedback

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

Michael Jumper reassigned GUACAMOLE-567:
----------------------------------------

    Assignee: Michael Jumper

> Network connection problem acknowledgement/feedback
> ---------------------------------------------------
>
>                 Key: GUACAMOLE-567
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
>             Project: Guacamole
>          Issue Type: Improvement
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: internal-error.png
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it should acknowledge this and unobtrusively notify the user. Lacking such notification, slow networks or remote desktop failures look like Guacamole bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript, but the error code is not recognized by the Guacamole client. The unknown error is thus translated into a generic "An internal error has occurred ..." message, which is obviously incorrect:
> !internal-error.png|width=320!



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