not geting the tunnel id

[TecCurious]

there should be a dedicated fucntion or event which return the tunnel ID which is return by the guacd with ready statement "5.ready,37.$3a672e7b-d8bd-4e89-9965-0bec79f42218;".
which is important to strore to connect existing connection or close connection.

[vadimpronin]

Can you describe in more details where and how you are going to use the tunnel ID?

[TecCurious]

when we create a ssession then guacd creates send the ready intruction with it's tunnel id "5.ready,37.$3a672e7b-d8bd-4e89-9965-0bec79f42218;". in this form.

If We want to join an already created tunnel as a seccond user then we have pass this $3a672e7b-d8bd-4e89-9965-0bec79f42218 unique ID to join that tunnle as a second user of the same created tunnel by the first user.
In other words if we want to share the session with other user then we have to use this Unique ID.

If we want to terminate the session from other user like Admin then also we have to pass this ID to terminate the tunnel.

[vadimpronin]

Sorry for closing this too early.
This change requires a lot of refactoring. I've started working on it in the latest master branch, and at least the connection ID (aka tunnel ID) is now properly transferred to the client via WebSockets.
However, there is still no functionality to connect a second user to the same connection. I’ll try to add that a bit later.

[TecCurious]

Thanks for the update, @vadimpronin! I appreciate you reopening this and working on the refactoring.

[vadimpronin]

@TecCurious I've implemented sending the connection id to the client. Using this id you can now also join existing connection (this feature was added and documented). I haven't published the new version yet, for now this new code is only in master. Can you checkout to the latest master and see if this is what you needed and that it works for you?