On Fri, Apr 15, 2011 at 8:14 AM, Martin Sustrik wrote:
> It's just review. I'll send you the cherry-pick once it is committed.
Ack. FWIW, it's easier to review code/patches if they're inlined
rather than attached to the email.
-Pieter
___
zeromq-dev m
On Fri, Apr 15, 2011 at 8:09 AM, Martin Sustrik wrote:
>>> And yes, there's a line missing in zmq_send(3) describing the behaviour.
> Theline is is *missing*. I've just sent the documentation patch to the ML.
> Feel free to propose better wording.
:-) I missed the 'missing' part.
Yes, the docu
On 04/15/2011 08:13 AM, Pieter Hintjens wrote:
> This is a useful change to the zmq_send(3) man page.
>
> I'm not sure if these patches you're sending to the list are just for
> review or meant also to be applied to 2.1& 2.2?
>
> If just review, could you please send me cherry-picks for the 2.x
>
This is a useful change to the zmq_send(3) man page.
I'm not sure if these patches you're sending to the list are just for
review or meant also to be applied to 2.1 & 2.2?
If just review, could you please send me cherry-picks for the 2.x
branches as previously?
Thanks
Pieter
On Fri, Apr 15, 201
On 04/15/2011 08:07 AM, Pieter Hintjens wrote:
> On Fri, Apr 15, 2011 at 7:02 AM, Martin Sustrik wrote:
>
>> You can use zmq_msg_copy function which "copies" the message by incrementing
>> the reference count of the buffer rather than by performing a memory copy.
>>
>> And yes, there's a line miss
On Fri, Apr 15, 2011 at 7:02 AM, Martin Sustrik wrote:
> You can use zmq_msg_copy function which "copies" the message by incrementing
> the reference count of the buffer rather than by performing a memory copy.
>
> And yes, there's a line missing in zmq_send(3) describing the behaviour.
I've che
>From 452ea97f5bb1bdd4d5ba76279de4189e8b8e5662 Mon Sep 17 00:00:00 2001
From: Martin Sustrik
Date: Fri, 15 Apr 2011 08:03:26 +0200
Subject: [PATCH] zmq_send(3) manpage improved
Signed-off-by: Martin Sustrik
---
doc/zmq_send.txt |4
1 files changed, 4 insertions(+), 0 deletions(-)
dif
2011/4/14 Martin Sustrik :
> On 04/15/2011 07:09 AM, 机械唯物主义 : linjunhalida wrote:
>> I install it on the third PC, and it still not work?
>> any one knows why? or nobody use zeromq under windows?
If the egg does not work for you, try building libzmq+pyzmq from
source, as detailed here:
http://www.
Drew,
/cygdrive/c/build/libzmq/tests$ ./test_shutdown_stress.exe
Software caused connection abort
nbytes != -1 (tcp_socket.cpp:214)
Aborted (core dumped)
Good spot! There's a bug with handling error codes from accept on
Cygwin. Try to apply the following patch and let me know whether it helps
On 04/15/2011 07:09 AM, 机械唯物主义 : linjunhalida wrote:
> I install it on the third PC, and it still not work?
> any one knows why? or nobody use zeromq under windows?
I have no experience with pyzmq on windows, but I would expect you need
to set some paths to make it work properly.
Martin
On 04/14/2011 05:22 PM, Pieter Hintjens wrote:
> On Mon, Apr 11, 2011 at 11:48 AM, Martin Sustrik wrote:
>
>> The problem with zmq_msg_t is that it's on the critical path. The
>> structure itself is very compact and has no space for a runtime tag.
>> Also the code dealing with it is highly optimis
I install it on the third PC, and it still not work?
any one knows why? or nobody use zeromq under windows?
2011/4/14 机械唯物主义 : linjunhalida :
> hello, I'm installing zeromq under windows,
> I use python2.6 (pythonxy), and I run:
>
> c:> easy_install pyzmq
>
> Searching for pyzmq
> Best match: pyzm
On 04/14/2011 05:03 PM, Berasategui Velasco, Asier wrote:
> Here is the complete error message:
>
> Assertion failed: msg_->flags& ZMQ_MSG_MORE (req.cpp:87)
>
> I don't have more information yet.
> I will continue looking for more info about this issue.
If you can post a binary log of the convers
On 04/14/2011 06:52 PM, Pieter Hintjens wrote:
> To send the same message multiple times you have to copy the message
> and send each copy once.
You can use zmq_msg_copy function which "copies" the message by
incrementing the reference count of the buffer rather than by performing
a memory copy
Based on what I am seeing, the EJB's don't support JNI calls. Its
explicitly discouraged in the spec, but not all the containers add the
security to disable access. The odd thing is that it looks like it links
correctly, but dies on the send.
Joshua
On 4/14/2011 5:34 AM, Marko Mikulicic wrote
On Thu, Apr 14, 2011 at 7:04 PM, Andrew Hume wrote:
> somehow it seems that i should be able to figure that out
> from the man pages, but i'm not sure which ones to amend.
It should be specified in the zmq_send[3] man page but isn't, for
reasons I'm not aware of.
In the Guide I do explain this
thanks.
somehow it seems that i should be able to figure that out
from the man pages, but i'm not sure which ones to amend.
On Apr 14, 2011, at 9:52 AM, Pieter Hintjens wrote:
> On Thu, Apr 14, 2011 at 6:37 PM, Andrew Hume wrote:
>
>> can i send a message multiple times safely?
>
> No, this do
On Thu, Apr 14, 2011 at 6:37 PM, Andrew Hume wrote:
> can i send a message multiple times safely?
No, this does not work. I've suggested a ZMQ_REUSE flag on send() that
would allow it.
To send the same message multiple times you have to copy the message
and send each copy once.
-Pieter
___
can i send a message multiple times safely?
that is, will
zmq_msg_init
zmq_recv(s1)
zmq_send(s2)
zmq_send(s3)
zmq_msg_close
(all with teh same message) work in the obvious way?
that is, the message gets safely sent on sockets s2 and s3
before anything gets
I'm working with Cygwin 1.7.8. This is from git master,
commit 5444064c1a195daee5e57eb996157393a4eed796:
make[2]: Entering directory `/cygdrive/c/build/libzmq/tests'
PASS: test_pair_inproc.exe
PASS: test_pair_tcp.exe
PASS: test_reqrep_inproc.exe
PASS: test_reqrep_tcp.exe
PASS: test_hwm.exe
PASS: t
On Mon, Apr 11, 2011 at 11:48 AM, Martin Sustrik wrote:
> The problem with zmq_msg_t is that it's on the critical path. The
> structure itself is very compact and has no space for a runtime tag.
> Also the code dealing with it is highly optimised and presumably should
> not do any additonal memor
On Wed, Apr 13, 2011 at 6:31 PM, Vitaly Mayatskikh
wrote:
> In fact, I desire incompatible changes in zmq 3.0, because I don't
> like current lisp bindings and want to change them in incompatible way
> ;)
Feel free to provide new Lisp bindings at any point. People have done
this (broken compatib
Here is the complete error message:
Assertion failed: msg_->flags & ZMQ_MSG_MORE (req.cpp:87)
I don't have more information yet.
I will continue looking for more info about this issue.
Thanks
Asier Berasategui
Unidad de Sistemas Industriales - Departamento de Control y TIC
TECNALIA
Paseo Mike
On 14 April 2011 05:33, Joshua Foster wrote:
> Has anyone had success using zeromq in a J2EE application?
>
Yes, I used it to quickly (1 day work) bypass a scalability issue on by java
stack (jetty->cxf->solr) and
reach 800 query-per-sec rate using a nodejs proxy on a 8 core machine
previously 5
24 matches
Mail list logo
