Reported by bluey on 8 Oct 2007 03:14 UTC
Be nice to use TCP for communication with the service, allowing for remote access and easier porting of the daemon to windows. First step would be to make socketName only accessible to the daemon, and provide an API for clients to connect and request a mapping to a port based on a request string. Ideally, in the future we would support both unix sockets and tcp sockets, and possible windows named pipes.
Well, we now can handle windows named pipes, and given another implementation of pipes.h we could probably support TCP without a problem. That requires a couple changes though. Specifically, we would need to create a struct with function pointers that would be loaded at start time so we could listen on multiple interfaces at the same time.
Reported by bluey on 8 Oct 2007 03:14 UTC Be nice to use TCP for communication with the service, allowing for remote access and easier porting of the daemon to windows. First step would be to make socketName only accessible to the daemon, and provide an API for clients to connect and request a mapping to a port based on a request string. Ideally, in the future we would support both unix sockets and tcp sockets, and possible windows named pipes.
Well, we now can handle windows named pipes, and given another implementation of pipes.h we could probably support TCP without a problem. That requires a couple changes though. Specifically, we would need to create a struct with function pointers that would be loaded at start time so we could listen on multiple interfaces at the same time.