Changes between Initial Version and Version 1 of Ticket #53


Ignore:
Timestamp:
12/23/09 10:07:38 (14 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #53

    • Property Owner changed from Antoine Martin to Antoine Martin
    • Property Status changed from new to accepted
  • Ticket #53 – Description

    initial v1  
    33We can export these displays to a remote server by getting the server to give us a remote port and setting up a reverse tunnel to a local port on the client (reserved for nx shadow process).
    44When we request connection (detect local access and use a shortcut - or even warning if same display as current), get the client to start the nx shadow, then it sends the session to the actual client.
     5
     6Since we may want to export many local displays to a single remote server, we should add these X sessions to the server and let the server provide the remote port (as per usual in an 'add_session' message). Then on the client which owns this display we simply forward the display to that port (rather than that port back to a local port). The status of the session should be 'starting' on the server until the client updates it to 'available' once the tunnel is ready. For connecting: the server should ask the client to start nxagent, once that is done the client can set 'connecting' OR just send the session to the client that requested it.
     7
     8We should also deal with clients connecting to local displays remotely exported more cleverly by not using 2 tunnels! (just detect this is local and connect directly).