See: https://github.com/zeromq/zyre/blob/master/src/zyre_node.c#L369
Who is supposed to receive the signal which is send when STOP is
received in zyre_node.c?
I'm guessing a zyre client sends STOP to zyre_node backend and waits for
reply through zsock_wait... however zyre_stop doesn't do
You're not missing anything, it's a bug... I've just sent a PR:
https://github.com/zeromq/zyre/pull/294
Thanks for catching this.
On Mon, Nov 17, 2014 at 10:55 AM, Arnaud Loonstra arn...@sphaero.org wrote:
See: https://github.com/zeromq/zyre/blob/master/src/zyre_node.c#L369
Who is supposed to
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
OK, here's my proposal: https://github.com/zeromq/libzmq/pull/1258
On Wed, Nov 12, 2014 at 9:24 AM, Frank Hartmann sound...@gmx.net wrote:
Pieter Hintjens p...@imatix.com writes:
That bug hasn't been fixed IMO.
So what you're saying is that simply doing a sleep (n) inside
zmq_ctx_term would
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
Everyone--
Just 3 questions/documentation nits/etc... Is it preferred that I write
them
all into a single message like this, or is it better to write 3 different
messages, one per issue? (Oooops, now it's 4!)
First, let me say, I am impressed with the new zsock features, as outlined
in the
czmq
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
Yet another C++ binding.
This version follows the design and conventions of Boost's Asio (see
http://www.boost.org/doc/libs/1_57_0/doc/html/boost_asio.html) library and
integrates ZeroMQ sockets into Asio's reactor machinery. It is licensed
under the same terms as Boost Asio (BOOST1.0 license).
Hi Steve,
all into a single message like this, or is it better to write 3 different
messages, one per issue? (Oooops, now it's 4!)
As long as the questions are simple, this is fine.
1.What is the preferred way to shut down a zsock?
Just destroy, unless you want to reuse the port or are
Hi Thomas,
Nice stuff! Here's the relevant page: http://zeromq.org/docs:organization
-Pieter
On Mon, Nov 17, 2014 at 6:06 PM, Thomas Rodgers rodg...@twrodgers.com wrote:
Yet another C++ binding.
This version follows the design and conventions of Boost's Asio (see
Nice stuff!
Thanks!
Here's the relevant page: http://zeromq.org/docs:organization
- Ask on zeromq-dev and you'll be welcomed into the organization owners'
team.
Looking back on my first message, it's not terribly explicit, apologies for
that.
I would like to contribute aziomq
Oh, i forgot the most important part. I need your GitHub account name.
Usually I can get this from your project, but you've committed the
code with zero history...
On Tue, Nov 18, 2014 at 1:09 AM, Thomas Rodgers rodg...@twrodgers.com wrote:
Nice stuff!
Thanks!
Here's the relevant page:
And when I mean zero history, I actually mean you're not committing
with an email address GitHub recognizes and can link to an account.
On Tue, Nov 18, 2014 at 8:55 AM, Pieter Hintjens p...@imatix.com wrote:
Oh, i forgot the most important part. I need your GitHub account name.
Usually I can
14 matches
Mail list logo
