Re: [zeromq-dev] Defaulting to tweetnacl?

2016-02-11 Thread Benjamin Henrion
On Thu, Feb 11, 2016 at 9:36 AM, MinRK wrote: > I think tweetnacl by default makes sense. +1 -- Benjamin Henrion FFII Brussels - +32-484-566109 - +32-2-3500762 "In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment

Re: [zeromq-dev] Defaulting to tweetnacl?

2016-02-11 Thread MinRK
I think tweetnacl by default makes sense. On Wed, Feb 10, 2016 at 11:40 PM, Pieter Hintjens wrote: > Hi all, > > I'd like to start moving to tweetnacl as the default when building > libzmq. This means, no separate install of libsodium, and encryption > built in by default. We

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Mark Gillott
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. > > > > > >

Re: [zeromq-dev] Defaulting to tweetnacl?

2016-02-11 Thread Luca Boccassi
Hi, I'm looking at it. Kind regards, Luca Boccassi On 11 February 2016 at 17:30, Pieter Hintjens wrote: > BTW I've also broken Travis builds, as --with-tweetnacl is no longer valid. > > The correct model should be: > > - default build (uses tweetnacl) > - libsodium bulld

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Doron Somech
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

Re: [zeromq-dev] Multi subscribe and single unsubscribe

2016-02-11 Thread Axel Voitier
That is the expected behaviour, yes. Subscriptions are said to be additive and idempotent. That is, if you subscribe twice to the same topic you have to unsubscribe twice to stop receiving it (provided it is not matched by another subscribe). Cheers, Axel -- Contact: axel.voit...@gmail.com

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Luca Boccassi
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

[zeromq-dev] Multi subscribe and single unsubscribe

2016-02-11 Thread Navneet Kumar
Hello everyone, I was testing with PUB-SUB and found that When I subscribe to a topic twice, then unsubscribe once, and again subscribe I receive all messages. Messages queued at the PUB when I unsubscribed only once. However if I unsubscribe twice or subscribe only once and unsubscribe once. I

Re: [zeromq-dev] Multiplexing a TCP endpoint

2016-02-11 Thread Alex Bligh
On 10 Feb 2016, at 19:11, Tom Quarendon wrote: > This is what "resources" in ZMTP 3.1 were designed for. No implementation yet > though (see other discussion on his list) :-) Thanks. That is pretty much exactly what I was looking for (other than the 'no

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Mark Gillott
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) > >

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Doron Somech
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

Re: [zeromq-dev] Access to underlying Linux socket?

2016-02-11 Thread Luca Boccassi
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

Re: [zeromq-dev] Defaulting to tweetnacl?

2016-02-11 Thread Pieter Hintjens
Just a follow up, I've cleaned up the tweetnacl code, which was a bit of a disaster. It's now in the src directory as tweetnacl.c and .h and conforms to expectations of the rest of the codebase. -Pieter On Thu, Feb 11, 2016 at 9:40 AM, Benjamin Henrion wrote: > On Thu, Feb

Re: [zeromq-dev] Defaulting to tweetnacl?

2016-02-11 Thread Pieter Hintjens
BTW I've also broken Travis builds, as --with-tweetnacl is no longer valid. The correct model should be: - default build (uses tweetnacl) - libsodium bulld (separate) If no-one takes this on I'll give it a shot asap. -Pieter On Thu, Feb 11, 2016 at 6:22 PM, Pieter Hintjens