Bug 1981

Summary: Support to automatically connect to nearest cluster
Product: ThinLinc Reporter: Peter Åstrand <astrand>
Component: VSM ServerAssignee: Peter Åstrand <astrand>
Status: NEW ---    
Severity: Enhancement CC: simon.marchi
Priority: P2    
Version: 1.5.0   
Target Milestone: LowPrio   
Hardware: PC   
OS: Linux   
Acceptance Criteria:

Comment 1 Erik Forsberg cendio 2006-05-05 11:28:43 CEST 
I wouldn't be surprised if there is some kind of support for this in for example
SLP (Service Location Protocol).
Comment 2 Peter Åstrand cendio 2013-05-08 10:53:48 CEST 
The general idea, as we understand it, is to have several clusters on different
geographical locations, and then have the system automatically select the
nearest cluster. Tarantella has/had something like this. 

I think this could be implemented in several ways. Some ideas:

* Add this functionality to VSM and perhaps construct some kind of "super VSM
server". 

* Use DNS in some clever way. Either we could provide a special DNS server which
returns different IPs depending on the client IP/distance/latency. Or, we could
perhaps use a standard DNS server returning multiple adresses and then add
functionality to client to determine which adress is nearest/fastest.
Comment 5 Pierre Ossman cendio 2024-03-14 10:55:20 CET 
This might be important if a cloud provider wants to deploy ThinLinc. They generally have data centers all over the world, and might want to offer a global service. Routing users to the data center with a reasonable latency is then key.