On Wed, 2016-02-10 at 23:33 +, Luca Boccassi wrote:
> On Feb 10, 2016 20:39, "Mark Gillott" wrote:
> >
> > On Wed, 2016-02-10 at 20:45 +0100, Pieter Hintjens wrote:
> > > You can't do this really, since one ZeroMQ socket can map to 0..n
> > > system sockets.
> > >
> >
>
You can actually use monitoring for this. Event socket accepted. Maybe a
socket option that accept function that create the underlying socket.
On Feb 11, 2016 18:50, "Luca Boccassi" wrote:
> On 11 February 2016 at 15:27, Doron Somech wrote:
> > What
On 11 February 2016 at 09:32, Mark Gillott wrote:
> On Wed, 2016-02-10 at 23:33 +, Luca Boccassi wrote:
>> On Feb 10, 2016 20:39, "Mark Gillott" wrote:
>> >
>> > On Wed, 2016-02-10 at 20:45 +0100, Pieter Hintjens wrote:
>> > > You can't do this
On Wed, 2016-02-10 at 23:33 +, Luca Boccassi wrote:
> > > There is a new option on libzmq master that lets you pre-configure
> a
> > > FD and give it to ZeroMQ to use for its first pipe. (ZMQ_USE_FD).
> > >
> >
> > Care to expand a bit more? Is there something (test code? source
> module)
> >
What is the specific option you need? Just make a socket option and apply
before connect. Like tcp keep alive and ipv6.
On Feb 11, 2016 15:12, "Mark Gillott" wrote:
> On Wed, 2016-02-10 at 23:33 +, Luca Boccassi wrote:
> > > > There is a new option on libzmq master that
On 11 February 2016 at 15:27, Doron Somech wrote:
> What is the specific option you need? Just make a socket option and apply
> before connect. Like tcp keep alive and ipv6.
Hi Doron,
The problem is that, for the use case we have, we use it with an
internal build of the
Mark,
As a comment from the peanut gallery, it is generally a bad thing to
leak that information up the protocol stack. Rather than getting that
information back, it might be better to be able to attach user callout
hooks at the places where you would want to make changes. That way there
is
You can't do this really, since one ZeroMQ socket can map to 0..n
system sockets.
There is a new option on libzmq master that lets you pre-configure a
FD and give it to ZeroMQ to use for its first pipe. (ZMQ_USE_FD).
A custom hook to configure new sockets is a nice idea.
-Pieter
On Wed, Feb
On Wed, 2016-02-10 at 20:45 +0100, Pieter Hintjens wrote:
> You can't do this really, since one ZeroMQ socket can map to 0..n
> system sockets.
>
Had a feeling that was going to be the case.
> There is a new option on libzmq master that lets you pre-configure a
> FD and give it to ZeroMQ to use
There is a test case (and a man page) on libzmq/master, search for
ZMQ_USE_FD in zmq_setsockopt.
On Wed, Feb 10, 2016 at 9:38 PM, Mark Gillott wrote:
> On Wed, 2016-02-10 at 20:45 +0100, Pieter Hintjens wrote:
>> You can't do this really, since one ZeroMQ socket can map to
On Feb 10, 2016 20:39, "Mark Gillott" wrote:
>
> On Wed, 2016-02-10 at 20:45 +0100, Pieter Hintjens wrote:
> > You can't do this really, since one ZeroMQ socket can map to 0..n
> > system sockets.
> >
>
> Had a feeling that was going to be the case.
>
> > There is a new
11 matches
Mail list logo