[nanomsg] Re: Port sharing, tcpmux, web-related roadmap et c.

  • From: Matthew Hall <mhall@xxxxxxxxxxxxxxx>
  • To: nanomsg@xxxxxxxxxxxxx
  • Date: Thu, 20 Nov 2014 13:57:19 -0800

On Thu, Nov 20, 2014 at 08:19:58AM +0100, Martin Sustrik wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Yes, it has to stay on, so that new connections can be established in
> the future. Maybe the best way to deal with it would be to start the
> daemon at the operating system boot time and just leave it running all
> the time.
> 
> For those who, for whatever reason, can't run the daemon as a separate
> process, there's an API to start it within the current process
> ("nn_tcpmux(5555);") but that's kind of ugly, given that even it that
> case the daemon is still a system-wide resource.
> 
> Martin

Could we use Coverity Scan: https://scan.coverity.com/ to check the daemon for 
any security problems, etc.?

In general a port-mapping daemon is helpful to making dependable distributed 
applications... Java uses JNDI for this among other mechanisms. There are 
various Amazon S3 based mechanisms for doing service location in the cloud, 
there is SLP, etc. etc.

Are there ways to get the daemon to open ephemeral / proxied sockets (not sure 
what the proper word is), from a known-good range where FW ACL's are open? Can 
you get it to cycle through the predictable pool, and what happens when it 
empties the valid-socket pool?

Matthew.

Other related posts:

  1. Home
  2. nanomsg
  3. Archive
  4. 11-2014