In general the IP address is a bad fit for either "node identifier" or
"application identifier". It assumes that we're working on TCP/IP (or
UDP). If you use this in any serious way, your work becomes tied to
the "one node per box" scale.
Look at a framework like Zyre and you'll see what I mean. S
W dniu 2014-09-25 13:54, Goswin von Brederlow pisze:
> It might help if you would post a testcase that:
>
> a) actualy compiles
It actualy compiles on Windows. I think I should state it more clearly
in first post.
> b) doesn't involve undefined behaviour:
>
> (ii) select() may update
On Fri, Sep 26, 2014 at 3:10 AM, Goswin von Brederlow wrote:
> Pieter: Would it be possible to put all the examples of the guide into
> a git project and have them included in the auto compile done for
> every pull request?
The examples are in a subdirectory of the Guide git project, and we
coul
W dniu 2014-09-26 02:05, KIU Shueng Chuan pisze:
> Your code could be stripped down a lot:
> 1) PUB socket is only for sending. There's no need to test it for
> ZMQ_POLLIN.
> 2) PUB socket never blocks when sending. There's no need to test it for
> ZMQ_POLLOUT.
> 3) SUB socket is only for receiving
I'm going to cut this thread down and reply minimally:
> And since you asked for it let me complain about this here. :) Maybe
> http://api.zeromq.org/4-1:zmq-sendmsg could be removed from the table
> of contents (or moved to a deprecated section in the table of contents
> so it remains for referen
On Fri, Sep 26, 2014 at 09:51:50AM +0200, Pieter Hintjens wrote:
> On Fri, Sep 26, 2014 at 3:10 AM, Goswin von Brederlow
> wrote:
>
> > Pieter: Would it be possible to put all the examples of the guide into
> > a git project and have them included in the auto compile done for
> > every pull requ
On Fri, Sep 26, 2014 at 09:51:40AM +0200, Dorvin wrote:
> W dniu 2014-09-25 13:54, Goswin von Brederlow pisze:
> > It might help if you would post a testcase that:
> >
> > a) actualy compiles
> It actualy compiles on Windows. I think I should state it more clearly
> in first post.
With the includ
On Fri, Sep 26, 2014 at 09:55:59AM +0200, Dorvin wrote:
> W dniu 2014-09-26 02:05, KIU Shueng Chuan pisze:
> > Your code could be stripped down a lot:
> > 1) PUB socket is only for sending. There's no need to test it for
> > ZMQ_POLLIN.
> > 2) PUB socket never blocks when sending. There's no need t
On Fri, Sep 26, 2014 at 4:01 AM, Goswin von Brederlow wrote:
> And czmq has more of an OO design. So
> every data object has a send function. One isn't preferable over the
> other. They are all ment to coexist.
Sorry, just want to take this point. You triggered some PTSD now.
The old ZeroMQ v2
On Fri, Sep 26, 2014 at 10:37 AM, Goswin von Brederlow
wrote:
> If the two get merged then why not merge the zsock class with the
> libzqm socket structure. Use it as is for the zsock interface and cast
> it to void * for the sake of the old API. A true merge and not just
> layering the czmq API
W dniu 2014-09-26 10:39, Goswin von Brederlow pisze:
>>> a) actualy compiles
>> It actualy compiles on Windows. I think I should state it more clearly
>> in first post.
>
> With the includes for FD_SET missing and Sleep() undefined?
>
I don't know what Windows version and which build environment
On Fri, Sep 26, 2014 at 11:06:29AM +0200, Pieter Hintjens wrote:
> This is one of those rare roadmap / vision threads.
>
> Concretely all this has to happen first:
>
> - release 4.0.5 sometime very soon
> - release 4.1.0 RC sometime later
> - update Guide for 4.1
> - release CZMQ v3.0 RC
>
> I t
On Fri, Sep 26, 2014 at 11:25:37AM +0200, Dorvin wrote:
> W dniu 2014-09-26 10:39, Goswin von Brederlow pisze:
>
> >>> a) actualy compiles
> >> It actualy compiles on Windows. I think I should state it more clearly
> >> in first post.
> >
> > With the includes for FD_SET missing and Sleep() undefi
Conceptually I like the idea of czmq folding back into libzmq. While
requiring both llibzmq and czmq for a language binding that wraps czmq
isn't the end of the world, it is an additional complexity.
I very much look forward to the czmq 3.0 release, and I'm hoping to have
goczmq feature complete
"You can't just open a socket and get to work anymore."
I just wanted to say that I find this statement to be empirically false. I
just open a socket and get to work all the time.
I think this thread is getting fuzzy, and I don't know what the problem is
that it is trying to address anymore.
On
On Fri, Sep 26, 2014 at 11:36 AM, Goswin von Brederlow
wrote:
> One last thing and then I will get back to work.
Ah, work, that mysterious thing we do when we're not talking about it :-)
> The zring class in CZMQ I feel is still experimental and I would like
> to keep that in flux some more, ma
Hi,
I've taken over CVE handling for zeromq. There were two issues fixed
recently. Could you please assign a CVE to them?
Matthew Hawn found that libzmq (ZeroMQ/C++) did not validate the other
party's security handshake properly, allowing a man-in-the-middle
downgrade attack.
Code commit: https:
On Fri, Sep 26, 2014 at 01:46:20PM +0200, Pieter Hintjens wrote:
> On Fri, Sep 26, 2014 at 11:36 AM, Goswin von Brederlow
> wrote:
>
> > One last thing and then I will get back to work.
>
> Ah, work, that mysterious thing we do when we're not talking about it :-)
>
> > The zring class in CZMQ I
On Fri, Sep 26, 2014 at 6:20 PM, Goswin von Brederlow wrote:
> Do you actually need it?
After all the work, that's a sad question. What I see are too-large
patches done in "I want to try this yet I've not defined a clean
problem statement" directions, which stress other people, create lots
of di
On Fri, Sep 26, 2014 at 06:34:32PM +0200, Pieter Hintjens wrote:
> On Fri, Sep 26, 2014 at 6:20 PM, Goswin von Brederlow
> wrote:
>
> > Do you actually need it?
>
> After all the work, that's a sad question. What I see are too-large
> patches done in "I want to try this yet I've not defined a c
On Fri, Sep 26, 2014 at 7:50 PM, Goswin von Brederlow wrote:
> How much of the time was spend on merging zhash support into zring?
Ah, sure. That was a short job and can certainly be kicked out again later.
Sorry, my bad.
> I think what doesn't quite work right is this:
>...
That 'discuss' pa
Hi,
I just send a pull request for a reimplementation of the zring class
with a new API:
https://github.com/zeromq/czmq/pull/698
Note: I renamed the existing zring class to zhashring in case that is
still wanted by others.
The ztimeout class, for which I write the initial zring class, needs
I rejected your PR.
More explanation in my comment on github.
Please try to solve atomic problems we agree on and then make minimal
solutions to them. Yesterday I described "thrashing". Your PR is a
great example of thrashing. Please stop it, it is not enjoyable.
*** Minimal solutions to agreed
23 matches
Mail list logo
