[
https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155805#comment-17155805
]
Edgardo Rodriguez commented on GUACAMOLE-1126:
----------------------------------------------
[~manolan] IMHO it's not OK to rely on errors indefinitely...
I can't imagine any user standing in front of a browser waiting "for ever"
until a connection gets established... In this case it will be fine to discuss
maximum retries (in this proposal 4 rounds of 15 seconds totalling 1 minute).
In any case defining a "sane" parameter will get the user to wait X amount of
seconds and then if the upper limit was reached they will just need to tick on
"Reconnect" button which is pretty much effortless.
> Implement Maximum auto-reconnect attempts
> -----------------------------------------
>
> Key: GUACAMOLE-1126
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1126
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Reporter: Edgardo Rodriguez
> Priority: Minor
>
> Using guacamole for 60+ users I've realized that sometimes, RDP hosts "go
> away" because of hardware issues, dns issues, etc and users might not be
> aware of it.
> For example, they leave their computer with the browser open with session
> established and going on... When this happens, Guacamole tries to
> auto-reconnect every 15 seconds without any limitation (some times
> indefinitely) and also, SESSION TIMER is renewed because of fake? user
> activity.
> I've implemented a counter which allows automatic reconnection attempts for
> up to 4 tries. When tried 4 times, countdown timer is not further applied and
> so user is left with manual Reconnect dialog prompt as usual.
> I `ve not implemented a visual indication like 1/4 2/4,etc because it
> involves transalations and other "more complex" stuff.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
