Nick

Thank you for your reply.

Detailed information is also appreciated.

I have one more question.

Do you know the best way to check if you are receiving data from Guacd?

I want to know where the delay is occurring between the guacamole server and 
the client.

Thank you.

> 2021/01/16 の 10:34 に Nick Couchman <[email protected]> によって書かれました:
> 
>     On Fri, Jan 15, 2021 at 7:03 PM < [email protected] 
> mailto:[email protected] > wrote:
> 
>         > > 
> >         Hi!
> >         I will post for the first time. This is Tadashi.
> > 
> >         Guacamole sometimes becomes unstable. A message appears at the 
> > bottom right of the screen stating that the network is not stable.
> >         The message that the network is not stable is I would like to know 
> > what kind of processing is done inside guacamole to display it.
> > 
> >         (For example, the response between the client and guacamole is 
> > measured by some mechanism and monitored at a fixed threshold.)
> > 
> >     > 
>     I believe most of the work for this was implemented as a part of 
> GUACAMOLE-567:
> 
>     https://issues.apache.org/jira/browse/GUACAMOLE-567
> 
>     The following two pull requests are the client-side changes that enable 
> this:
> 
>     https://github.com/apache/guacamole-client/pull/290
>     https://github.com/apache/guacamole-client/pull/312
> 
>     Basically, if the connection does not receive any data from the tunnel 
> (guacd) within 1500 milliseconds, it warns that the connection is unstable. 
> If data is not received over the tunnel within 15000 milliseconds, the 
> connection is assumed to be lost and the client closes it.
> 
>     The second pull request adds a "ping" every 500 milliseconds (in the form 
> of a "nop" message) from the browser to the Java tunnel (which is then passed 
> on to the server) that insures that traffic is traveling over the tunnel.
> 
>     I'm sure Mike can provide more thorough detail on this, or you can have a 
> look at the source code of the files impacted by those pull requests.
> 
>     -Nick
> 

Reply via email to