Does anyone have a simple example of the upstream/downstream sockets? I've
looked at the butterfly example but its got a lot of meat to it (also I
think the code and tutorial are out of sync). I just want to see how to have
two objects (A and B), each with an upstream socket and downstream socket,
Dana,
> Does anyone have a simple example of the upstream/downstream sockets?
> I've looked at the butterfly example but its got a lot of meat to it
> (also I think the code and tutorial are out of sync). I just want to see
> how to have two objects (A and B), each with an upstream socket and
I looked at that but I wasn't sure how the end points should be setup for
the sockets since those come in as arguments to the executables. If I am
going to use them in an IPC fashion, would the endpoint simply be the same
for the in and out socket that I want connected?
Thanks,
Dana
On Wed, Jun 9
Hi Dana,
> I looked at that but I wasn't sure how the end points should be setup
> for the sockets since those come in as arguments to the executables. If
> I am going to use them in an IPC fashion, would the endpoint simply be
> the same for the in and out socket that I want connected?
I have
other than zmq_sleep and zmq_stopwatch being missing in 2.0.7 i ran
into another problem
in receive_replies.cpp, line 65 should declare a variable sync
containing an empty message.
ex.
zmq::message_t sync;
out_socket.send (sync);
right now i think its sending the address of the sync syscall ?
wi
Hi Martin,
On Wed, Jun 9, 2010 at 12:09 PM, Martin Sustrik wrote
> I believe the "send_requests" is the initial node of the pipeline. It
> produces request. Down the stream there's arbitrary number of
> "component"s which do the actual processing and generate replies.
> Further down there's "rec
Hi Joe,
> other than zmq_sleep and zmq_stopwatch being missing in 2.0.7 i ran
> into another problem
> in receive_replies.cpp, line 65 should declare a variable sync
> containing an empty message.
>
> ex.
> zmq::message_t sync;
> out_socket.send (sync);
>
> right now i think its sending the addr
nm, it seems the problem im having is unrelated. sometimes
receive_replies stops after half the messages and hence the sync never
gets sent, as its stuck in the for loop, i cant replicate it reliably
im running the commands as:
./send_requests tcp://127.0.0.1: tcp://127.0.0.1:5556 1000
./com
Peter Alexander wrote:
> Hi Martin,
>
> On Wed, Jun 9, 2010 at 12:09 PM, Martin Sustrik wrote
>
>> I believe the "send_requests" is the initial node of the pipeline. It
>> produces request. Down the stream there's arbitrary number of
>> "component"s which do the actual processing and generate re
On Tue, Jun 22, 2010 at 3:00 PM, Martin Sustrik wrote:
>
> I think we are missing this kind of discussion of pipeline paradigm in
> the documentation.
>
> Once I wrote this article:
>
> http://www.zeromq.org/tutorials:butterfly
>
> However is misses the overall introduction (and the code examples
10 matches
Mail list logo
