On Mon, Apr 23, 2018, 17:39 messido <[email protected]> wrote:
> Thanks for the quick response.. > > Yes that's correct, I am referring to a web application built off > gucamole-common-js.. > > Going with debug level = trace (for guacd), I can see that guacd is > awaiting > a "confirmation" from the user in order to keep connection alive.. No, it isn't waiting for confirmation from the user. It is waiting for any messages of any kind from the client. now if no > mouse/keyboard movements are sent, guacd will not receive a confirmation > which will terminate the connection after what i'm assuming is 15 - 30 > seconds.. > No, there are other messages exchanged besides keyboard and mouse events. In addition to sync responses (client acknowledgement of frame rendering), there is a "nop" keep-alive sent every 5 seconds: https://github.com/apache/guacamole-client/blob/57d81544ea46fc4f7e68836d146ca60022c430fa/guacamole-common-js/src/main/webapp/modules/Client.js#L1506-L1509 is there a way to send confirmations back to guacd even if the user does not > move mouse/keyboard? > This already happens automatically (see above). If your connection is timing out, it must be for a different reason. Unless you have made changes to the internals of the client, the most likely cause would be network disruption, such as a proxy between the user and the server. The user does not need to continuously move the mouse, press keys, etc. (which would make things fundamentally unusable). Simply having the connection open is sufficient. - Mike
