Hi Sergey, I would use push and pull sockets to let multiple parties talk to one server (server pulls to receive). Try Martin's new tcpmuxd for the naming part. Best, Jason > On Dec 18, 2014, at 3:42 AM, Sergey Skorokhod <skorokhod.sergey@xxxxxxxxx> > wrote: > > I am looking around possibility to organize simple listen server, which > accept all incoming connections and uses its own higher-level protocol to > identify each connection. Exchange with user could be done in both directions > like the pair protocol do. However, the point is that in the current nn_pair > protocol server should predefine connection name for each pair and client > should use connection names from this list. > > > > Is it possible to extend current nn_pair protocol to allow multiple > connections on server side for single bound socket url and identify > connections via endpoint, for example? > > > > -- > Regards, > Sergey Skorokhod >