Yeah, you always need one Socket to bind any used endpoint (i.e. address). Only then, one (or many) other Sockets which are connected to that endpoint will be able to communicate over that endpoint.
Technically, it does not matter, which Dealer is binding, this is a design decision you have to do yourself (for example if you send Textures from many devices to one machine, you’d bind the receiver, if you send Textures from one device to many, you’d bind the sender)
ask yourself, what kind of communication is it, if you consider scaling up from the beginning
if it is a 1:1 relation, you might want to use two Pair (Network ZSocket), but trust me, that hardly ever scales well.
if it is 1:n or n:1, you will need to Bind the 1, but not the n
if you find yourself in need of an advanced n:n situation, it will be necessary to dissolve it into a n:1 <-> 1:n situation (kindly helped by Proxy (Network ZSocket))).
A few weeks back I was talking about this Configuration setting in Inspector with joreg. I thought, that it is ok to be only accessible with Herr Inspector, because one has to decide what to bind very conciously, instead of just switching it on and off until it works.
Would it have helped you, if the Bind choice would have been a regular pin?
Streaming Texture ZeroMQ.v4p (23.2 kB)