Martin,
Was there any conclusion about how to handle identity errors? Right
now it's trivial to crash a peer by connecting twice with the same
identity. There are two issues for this,
http://github.com/zeromq/zeromq2/issues/#issue/30 and
http://github.com/zeromq/zeromq2/issues/#issue/65.
Is the
On Mon, Sep 6, 2010 at 10:07 PM, Martin Lucina wrote:
> There is one catch, which is that I have no idea how the "derived work"
> interacts with the "static linking exception". My guess is that it doesn't
> and that would be a problem, but IANAL and I suggest you get advice from a
> FOSS licensin
Hi Ilja,
Works ok with master branch, but there's a bug in initializing
zmq::context_t with 0 io threads.
I've attached following patch,
diff --git a/src/ctx.cpp b/src/ctx.cpp
index 65c5316..ec8a045 100644
--- a/src/ctx.cpp
+++ b/src/ctx.cpp
@@ -64,7 +64,7 @@ zmq::ctx_t::ctx_t (uint32_t io_thread
I've got about 2,000 threads talking over REQ ports inproc to a single XREP
port.
Any thoughts as to whether this might be the cause of performance hiccups under
2.0.7? I'm polling the XREP and a few other ports in my main loop, and have
already raised the device to SCHED_RR ... I believe the
Hi Hi,
OpenPGM 5.0 now provides a Berkeley sockets based API to reduce the
learning curve for developers creating new solutions using the PGM reliable
multicast network protocol.
http://openpgmdev.blogspot.com/2010/09/miru-announces-openpgm-5.html
Unit, network, performance, and unit performan
Pieter,
p...@imatix.com said:
> Mato,
>
> Sigh. You're right, I'm wrong on this. Of course when a modified
> version of 0MQ is published via github, it creates an LGPLv3 derived
> work under section 5 of the GPLv3 that we can re-incorporate as we
> like.
>
> Sorry... don't know how I missed so
On Mon, Sep 6, 2010 at 11:45 AM, Brian Granger wrote:
> On Sat, Sep 4, 2010 at 4:10 PM, Timothy Fitz
> wrote:
> > For those of you looking for Twisted ZeroMQ integration, I've built out
> the
> > "Write a zmq_poll-based reactor" idea here:
> > http://github.com/TimothyFitz/ZMQReactor
> > It succ
Mato,
I am actually on vacation/holiday this week, could you file an issue
on github for me to track this:
http://github.com/zeromq/pyzmq/issues
Next week when i return I am going to be doing some pyzmq work and
should be able to look at this.
Cheers,
Brian
On Fri, Sep 3, 2010 at 2:56 PM, Jon
Timothy,
This is great! Let's keep in touch if you need anything done to pyzmq
to support this. I have used Twisted a lot and it would be very nice
to have zmq support in twisted.
On Sat, Sep 4, 2010 at 4:10 PM, Timothy Fitz wrote:
> For those of you looking for Twisted ZeroMQ integration, I'v
On Mon, Sep 6, 2010 at 8:39 PM, Chuck Remes wrote:
> Sorry, wrong list!
MongoDB? :-)
-
Pieter Hintjens
iMatix - www.imatix.com
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Martin,
I totally respect your choices on this one. A few notes below...
On Sun, Sep 5, 2010 at 12:26 AM, Martin Sustrik wrote:
> Hi Brian,
>
>> Another reason I would like to get this in to a 2.0.9 release is that
>> 2.1 involves lots of new changes that are likely to make things
>> unstable f
Sorry, wrong list!
cr
On Sep 6, 2010, at 1:38 PM, Chuck Remes wrote:
> I have to do a rolling upgrade across my servers. Is it safe to have a mix of
> 1.6 and 1.4 servers in a master/slave configuration where the master is 1.6.2?
>
> cr
>
> ___
> ze
I have to do a rolling upgrade across my servers. Is it safe to have a mix of
1.6 and 1.4 servers in a master/slave configuration where the master is 1.6.2?
cr
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/list
On Mon, Aug 30, 2010 at 6:37 AM, Moritz Rosenthal wrote:
> Hi!
>
> at #zeromq they said it might be of interest to some receivers of this
> list, so I'm gonna tell my short story of try, error and success.
>
> How I built 0MQ for my embedded ARM:
>
> First I wanted to try it at my PC. So I used th
Hello, David!
Am I right you have a subscriber up and running?
Otherwise tshark cannot observe anything since there is no established
TCP session and your process is just awaiting for an incoming TCP connection
and you can probably prove it with the help of netstat.
"Publisher" implies informati
Hello!
Trying to understand how 0mq works I am not sure I properly got how
multithreading is handled.
For example in yqueue_t::push I can see
==
if (++end_pos != N)
==
though I did not find any attempt to ensure (e.g. by means of memory barriers
or volatile keyword)
this variable, modified by m
hello,
I have a simple test case here that mirrors what i am doing in my main
project. I need to publish messages from several worker threads, so I
have a socket to connect to an ipc pipe from each thread and then a
forwarder device to forward from the backend socket to the main
publisher socket
0MQ does its own framing for all messages. When you call recv(), it returns
with a whole message or nothing at all. Same thing with polling: if it signals
that you can do a recv(), it is because there is at least a whole message
waiting to be read. Hope that helps.
Gonzalo Diethelm
___
On Mon, Sep 6, 2010 at 12:23 AM, Martin Lucina wrote:
> p...@imatix.com said:
>> On Thu, Sep 2, 2010 at 6:03 PM, Martin Lucina wrote:
>>
>> > I noticed that when updating to the 2.0.8 PUSH/PULL you also removed the
>> > DOWNSTREAM/UPSTREAM constants. Was that deliberate?
>> >
>> > We have kept th
Hi,
In my current situation, I am reading bytes from an instance of
java.io.DataInputStream, extracting the length of the actual payload from
the first two bytes of input data, and reading that payload after that. I
would like to know if ZeroMQ, with its message-oriented philosophy, fits
with this
OK, I've cleaned the issue. It uses the MarkDown language so you
indent code by 4 spaces.
On Mon, Sep 6, 2010 at 4:57 PM, Ilja Golshtein wrote:
> 06.09.10, 18:18, "Pieter Hintjens" :
>
>> Hi Ilja,
>>
>> Can you please log this on the 0MQ issue tracker at
>> http://github.com/zeromq/zeromq2/iss
06.09.10, 18:18, "Pieter Hintjens" :
> Hi Ilja,
>
> Can you please log this on the 0MQ issue tracker at
> http://github.com/zeromq/zeromq2/issues, thanks.
Unfortunately I failed to manage markup properly, so
http://github.com/zeromq/zeromq2/issues/#issue/64
is practically unreadable.
I've tr
Hi Ilja,
Can you please log this on the 0MQ issue tracker at
http://github.com/zeromq/zeromq2/issues, thanks.
-Pieter
On Mon, Sep 6, 2010 at 12:04 PM, Ilja Golshtein wrote:
> Hello!
>
> The application http://pastebin.com/yJY5xgts
> produces following trace
> ==
> (gdb) thread 1
> [Switching to
Mato,
Sigh. You're right, I'm wrong on this. Of course when a modified
version of 0MQ is published via github, it creates an LGPLv3 derived
work under section 5 of the GPLv3 that we can re-incorporate as we
like.
Sorry... don't know how I missed something so stunningly obvious.
OK, so we need
On Mon, Sep 6, 2010 at 12:05 PM, Martin Lucina wrote:
> Further, the policy you describe would require that "This commit is
> licensed under the MIT license" be included in the commit history itself,
> otherwise it wouldn't propagate in a distributed fashion.
Again, because you're still suggesti
Hello,
I think I can say for sure the crash caused by 0mq.
2.0.7 and 2.0.8 behave in the same way.
If put something like sleep(1) before the end of send_thread try block,
everything is fine.
Serialising of erasing push sockets in send_thread by mutex does not help
though.
Thanks.
06.09.10, 14
m...@kotelna.sk said:
> p...@imatix.com said:
> > On Mon, Sep 6, 2010 at 9:00 AM, Martin Lucina wrote:
> >
> > > Another reason we can't technically accept pull requests is due to the
> > > requirement by iMatix that patches are licensed under the MIT/X11 license.
> > >
> > > I believe that this
Hello!
The application http://pastebin.com/yJY5xgts
produces following trace
==
(gdb) thread 1
[Switching to thread 1 (Thread 2025)]#0 0x2abfca190265 in raise (
sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0
p...@imatix.com said:
> On Mon, Sep 6, 2010 at 9:00 AM, Martin Lucina wrote:
>
> > Another reason we can't technically accept pull requests is due to the
> > requirement by iMatix that patches are licensed under the MIT/X11 license.
> >
> > I believe that this is in the process of being changed t
On Mon, Sep 6, 2010 at 9:00 AM, Martin Lucina wrote:
> Another reason we can't technically accept pull requests is due to the
> requirement by iMatix that patches are licensed under the MIT/X11 license.
>
> I believe that this is in the process of being changed to pure LGPLv3+ with
> no separate
Hi Sebastian,
fen...@gmail.com said:
> I have made a few fixes to the spec to make in build on rhel6 using rpmbuild.
> See if you want to pull from there.
> http://github.com/zeromq/zeromq2/pull/61
Thanks for the fixes. Unfortunately, due to current licensing requirements
by iMatix I can't apply
p...@imatix.com said:
> On Thu, Sep 2, 2010 at 6:03 PM, Martin Lucina wrote:
>
> > I noticed that when updating to the 2.0.8 PUSH/PULL you also removed the
> > DOWNSTREAM/UPSTREAM constants. Was that deliberate?
> >
> > We have kept the old constants in the core zmq.h for backward
> > compatibili
m...@kotelna.sk said:
> Hi,
>
> lestr...@gmail.com said:
> > > So, from now on, all the contributors to zeromq2 repo, to both master
> > > and maint branches -- even those that had direct commit access in the
> > > past -- are going to send patches to the mailing list. I will then apply
> > > them
33 matches
Mail list logo
