Hmm... this would be more confusing than helpful IMO. 4.1.x should
normally go through the usual 'release candidate' - 'stable' process.
This would suggest we can randomly backport new functionality so long
as we update the version number. That isn't our process at all...
If adding
Excellent question. This isn't documented in the man pages; however
the code does re-resolve the address each time it attempts a
connection.
On Tue, Mar 18, 2014 at 8:47 PM, Ron ron.a...@gmail.com wrote:
Hi,
or will it always use the ip that it initially resolved to?
Thanks.
Ron
Hi All,
I'm trying to monitor ingress/egress messages from within the
application. Is there a way to get the number of queued messages on a
socket waiting to be delivered from 0MQ API?
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
There's no API for this, and it'd be hard to make in any case, as
message pipes are filled and emptied asynchronously by different
threads.
One way to control the limit of pending messages is to use credit
based flow control (see Chapter 7 of the Guide).
On Wed, Mar 19, 2014 at 1:59 PM, Reggie
Isn't this only in the master branch at the moment (PR 921) or was there some
additional logic for this that was present in earlier versions?
-Original Message-
From: zeromq-dev-boun...@lists.zeromq.org
[mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of Pieter Hintjens
Sent:
With a library like zeromq, there's no telling how much heavy lifting is
being done under the hood. The tutorial examples are all very
short-lived code snippets. In a real application that may run for weeks
or months, I wonder how best to handle the lifetime of a socket.
In the Common Lisp
zeromq-dev@lists.zeromq.org
X-Mailer: iPhone Mail (11D167)
I'm getting an invalid argument when I try using pgm w zmq 3.2.4 when my URL
looks like:
epgm://bond0;239.1.2.3:45678
If I remove bond0 it works fine.
Any idea why or how I can get more information on the error?
Thanks!
On Wed, Mar 19, 2014 at 12:56 AM, Pieter Hintjens p...@imatix.com wrote:
Hmm... this would be more confusing than helpful IMO. 4.1.x should
normally go through the usual 'release candidate' - 'stable' process.
This would suggest we can randomly backport new functionality so long
as we update
You're right, this is a week old.
On Wed, Mar 19, 2014 at 5:10 PM, Mark Barbisan mark.barbi...@evault.com wrote:
Isn't this only in the master branch at the moment (PR 921) or was there some
additional logic for this that was present in earlier versions?
-Original Message-
From:
I'm working on developing a framework for management and tasking of
remote administration agents. I've chozen zmq as my messaging library
since it is lean and gives me an abstraction that I like. Is this the
right place to ask about how I'm architecting the system or is there a
better venue?
10 matches
Mail list logo
