Suppose I have the zyre frontend socket in my app in a poller.
Every activity on the socket would then be handled by a method
retrieving the frames from the socket.
If I want to retrieve header info of a peer I would call
zyre_peer_header_value
However this call ends with retrieving messages
This is why in Zyre (and newer actor models) we use a second socket
for data transfer.
https://github.com/zeromq/zyre/commit/c684cad
-Pieter
On Mon, Nov 17, 2014 at 1:58 PM, Arnaud Loonstra arn...@sphaero.org wrote:
Suppose I have the zyre frontend socket in my app in a poller.
Every
On 11/17/2014 03:10 PM, Pieter Hintjens wrote:
This is why in Zyre (and newer actor models) we use a second socket
for data transfer.
https://github.com/zeromq/zyre/commit/c684cad
-Pieter
Thanks for the pointer, Pieter. I missed that one.
It's implemented in Pyre now as well.
Rg,
Arnaud
Great :-)
On Mon, Nov 17, 2014 at 4:23 PM, Arnaud Loonstra arn...@sphaero.org wrote:
On 11/17/2014 03:10 PM, Pieter Hintjens wrote:
This is why in Zyre (and newer actor models) we use a second socket
for data transfer.
https://github.com/zeromq/zyre/commit/c684cad
-Pieter
Thanks for the
