Session-specific Sockets

[nthallen]

This option allows for the creation of local session-specific servers. This is necessary to allow doit scripts targeting remote FlightNodes to run local memo and playbacksrvr instances to offload noise on the FlightNode and facilitate independent startup and shutdown of the user interfaces. While it is possible to run a local server, there is risk of collision if two or more GSE instances are run on the same machine at the same time. This is quite likely when a local user and a remote user are both displaying realtime data.

Strategy:

• Add a session option to server.oui and client.oui
• option has no effect when accessing a remote server
• session value is appended to the service name for Unix domain sockets

Need to sort out exactly how options would work.

Specifically, display programs need to access:

• tm_bfr for telemetry, usually on $FlightNode
• cmd/Quit, ideally on the local system and session-specific
• memo, ideally on the local system and session-specific

So, how to setup options?:

• separate options to identify hostname for each service
• assume there will be at most one remote host for the normal services, and provide options to specify local or remote for each service
• A common option for identifying hostname for all services
  • -Hsvc/subsvc:f.q.d.n
  • Store results in a hash
  • I think this approach gets way to complicated too quickly

[nthallen]

A different take on that last option would be tie the hostname to an application-specific function. The function could be the service name, if that is obvious, but might be something else if, for example, you need to distinguish between subservices. Suppose you have an application that needs to send commands to one hostname but wants to receive a Quit command from another. The app could define 'send' for the former function and 'recv' for the latter.