Re: [zeromq-dev] Which socket to choose?

2019-08-24 Thread Attila Magyari
> From: zeromq-dev On Behalf Of Brett > Viren via zeromq-dev > Sent: Tuesday, August 20, 2019 7:37 AM > To: Attila Magyari > Cc: Brett Viren; ZeroMQ development list > Subject: Re: [zeromq-dev] Which socket to choose? > > > [EXTERNAL EMAIL] > > Hi again, Attil

Re: [zeromq-dev] Which socket to choose?

2019-08-20 Thread Brett Viren via zeromq-dev
Hi again, Attila, Attila Magyari writes: > So having two sockets, one for sending and one for receiving is the way to > go? Disclaimer: I'm a zeromq amateur so take my advice as such. I don't know if this two-socket approach is best but it's certainly one way to do it. (For a design that

Re: [zeromq-dev] Which socket to choose?

2019-08-20 Thread Luca Boccassi
Look into router/dealer On Tue, 2019-08-20 at 08:28 +0300, Attila Magyari wrote: > Thanks Brett, > > So having two sockets, one for sending and one for receiving is the > way to go? > > By message order restrictions I meant the send/recv pattern to be > unrestricted, no mandatory order of

Re: [zeromq-dev] Which socket to choose?

2019-08-19 Thread Attila Magyari
Thanks Brett, So having two sockets, one for sending and one for receiving is the way to go? By message order restrictions I meant the send/recv pattern to be unrestricted, no mandatory order of send/recv. The server could send an arbitrary number of messages to the client. One-to-many as in

Re: [zeromq-dev] Which socket to choose?

2019-08-19 Thread Brett Viren via zeromq-dev
Attila Magyari writes: > Reading the docs all the other sockets seem to have extra restrictions or > complications, which would not meet my needs: > - bidirectional I assume you mean symmetrically bidirectional? If so, a pair of PUSH/PULL (or PUB/SUB) on each end would provide that. > - no