[
https://issues.apache.org/jira/browse/GUACAMOLE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187350#comment-17187350
]
Mike Jumper commented on GUACAMOLE-1165:
----------------------------------------
This sounds like it would be brittle. How would any connecting client,
including Guacamole, know that a particular port is not already in use by a
different user?
Even if a user's former connection were tracked and we know that there is no
longer any outbound connection from Guacamole to a particular port, there is no
guarantee that a different client has not established such a connection since
then, or that the user's desktop session is not still running in the
background, waiting for the connection to resume... Correct?
I'd think this is something that should be done by session management software
within the remote desktop server, not on the client or Guacamole side.
> Allocate VNC port sequentially for XDMCP
> ----------------------------------------
>
> Key: GUACAMOLE-1165
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1165
> Project: Guacamole
> Issue Type: New Feature
> Components: VNC
> Affects Versions: 1.2.0
> Reporter: Braihan Cantera
> Priority: Trivial
>
> In VNC connections, it would be useful to have a "*XDMCP*" toggle option
> which makes when enabled to automatically allocate VNC port to each new
> connection to XDMCP enabled servers so users can have multi sessions over VNC
> to linux servers.
> Example:
> * XDMCP: on
> * User1 connects to server1 via VNC connection, guacamole connects to
> server1:5900
> * User2 connects to server1 via VNC connection, guacamole connects to
> server1:5901
> * User1 and User2 can now use server1 in parallel leveraging XDMCP
> This would provide real multi session "remote desktop" experience to VNC
> connections in guacamole.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
