Morning Martin,
I forked the zguide project and sent you a pull request.
Just in case the examples are in this forked project:
https://github.com/gaubert/zguide
I might add more examples in the next 2 days as I continue to
experiment with zmq.
Let me know if you need some help.
Cheers Guillaume
Praveen,
On Tue, Dec 14, 2010 at 1:06 PM, Praveen Baratam
wrote:
> Dhammika,
> Any progress with this issue?
I was trying to recreate this, but no luck :-(
https://gist.github.com/743150/2e72d18c7f2c1274a21c7fd06f1aafc47ec9764e
Are you using language bindings?
Dhammika
Trying to re-remember how to obtain the return address for a given ZMQ
message, or the ZMQ representation thereof (a UUID or something). The
message originator might be behind a NAT system, so the originating
address could be useless (there are too many 192.168.0.1s in the world).
What I want t
Libev is a strictly Level-Triggered event loop wrapper. The author points
out that its is required for portability.
So the problem you mentioned does not arise as we are using Level-Triggered
event reactor.
Praveen
On Thu, Dec 16, 2010 at 12:08 AM, Martin Sustrik wrote:
> Hi Praveen,
>
> I thi
Mikko,
> gave it a quick spin and seems to work fine.
Applied to master.
Thanks!
Martin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
On Wed, Dec 15, 2010 at 1:21 PM, Martin Sustrik wrote:
> Please, check the patch and let me know whether it works for you.
>
> Martin
>
Hi,
gave it a quick spin and seems to work fine.
--
Mikko Koppanen
___
zeromq-dev mailing list
zeromq-dev@lists.z
Hi Praveen,
I think the problem may be in the fact that the ZMQ_FD is
edge-triggered, i.e. you get an event if you tried to read a message
unsuccessfully (EAGAIN) and the message arrives. When second message
arrives you get no event (unless you've tried to read it and got EAGAIN)
in the meanti
Hello All,
I started working on the external event loop integration for ZMQ sockets
using getsocketopt and ZMQ_FD. I am using a wrapper around Libev for the OS
specific event loop abstraction.
But the event loop is not working on FDs from ZMQ sockets. Its not returning
any events. Given below is
Hi,
I have implemented and tested the 3 examples from the zguide:
msgqueue.py : https://gist.github.com/742013
mtserver.py: https://gist.github.com/742065
mtrelay.py: https://gist.github.com/742178
It would be nice to have at least an acknowledgment of reception as I
have not received any comme
let me
add, that I poll() on two XREQ sockets and the involved SUB socket!^5 Sven
-
E = mc² ± 2dBA - everything is relative
-
-Original Message-
Date: Wed, 15 Dec 2010 17
Hi
all!
I have a queer behaviour in my services build on zmq. I tried to
write a minimal testcase, but failed to rebuild this bug in a smaller
program ;o(Hopefully my description is enough to find the
cause:I have a PUB/SUB socket, where several messages
already have passed successfully. As the las
Guillaume,
> Thanks for answering me.
> I have a github account so If you give me access to the zguide
> repository, I could create branch and put the examples there.
> Pieter will have a look at the examples in the branch and merge the
> "example" branch into the main one when he is back and if t
Hi Martin,
Thanks for answering me.
I have a github account so If you give me access to the zguide
repository, I could create branch and put the examples there.
Pieter will have a look at the examples in the branch and merge the
"example" branch into the main one when he is back and if the
transla
Hi Guillaume,
> It would be nice to have at least an acknowledgment of reception as I
> have not received any comments regarding my 2 previous example
> submissions.
>
> Let me know what you think about it and how to push it to the zguide
> git repository ?
Pieter, who's maintaining the guide is
Mikko,
> attached is a patch which removes assertions from devices and moves
> just returns -1 to the caller. This allows caller to handle a
> situation where device is interrupted.
Applied to master.
Thanks.
Martin
___
zeromq-dev mailing list
zeromq-d
Hi Mikko,
I've done some cleanup in the patch. Namely I've removed full() method
from swap_t and left fits(msg) as the only means to check whether swap
is writeable. Second, I've removed pipe_t::check_write() method and left
only pipe_t::check_write(msg) method. Third, I've modified the
imple
Morning,
I also have implemented the lruqueue2 example from the guide.
It is available for review here: https://gist.github.com/741784
Let me know what you think about it and how to push it to the git repository.
The code is licensed under the MIT/X11 license.
Let me know what you think.
Cheer
17 matches
Mail list logo