On Tue, Jan 25, 2011 at 1:12 AM, Benoit Chesneau wrote:
> I tbink you'r right. If I want to keep ly current pattern, what I want
> is probably xreq -> rep. The thing I'm not sure about is how the xreq
> socket deals with a disconnectd rep. What happend to the messge he
> has? Does it try to send
Hello All,
I have previously raised an issue on this mailing list that integration of
ZMQ sockets with external event loops is not working. You can review the
testcase from my previous mail to understand where and how its failing.
Here is a work around for this problem.
Actually when sockets are
On Tuesday, January 25, 2011, Pieter Hintjens wrote:
> On Mon, Jan 24, 2011 at 11:51 PM, Benoit Chesneau wrote:
>>
>> Hum I should be tired, PUSH/PULL works as expected. Now the only thing
>> I miss i s a way to remove a connection from the push socket. Ca I do
>> this ?
>
> Not really. If you wa
On Mon, Jan 24, 2011 at 11:51 PM, Benoit Chesneau wrote:
>
> Hum I should be tired, PUSH/PULL works as expected. Now the only thing
> I miss i s a way to remove a connection from the push socket. Ca I do
> this ?
Not really. If you want two-way communication and synchronization
between workers an
On Mon, Jan 24, 2011 at 11:54 PM, Benoit Chesneau wrote:
> Yes, but I may have missed something. So far I was under the
> impression I needed a broker Where I 'm trying to avoid that. But I
> may be wrong, back to the doc then, thanks.
Brokers can simplify architectures with many peers. They so
On Mon, Jan 24, 2011 at 11:49 PM, Pieter Hintjens wrote:
> Hi Benoit,
>
>> I would like to use zeromq as a way to send quick notify workers about
>> new tasks and I currently hesitate about the strategy to use.
>
> Have you read the Guide (http://zguide.zeromq.org/)? There are a
> bunch of routin
On Mon, Jan 24, 2011 at 11:39 PM, Benoit Chesneau wrote:
> PUSH/PULL seems what I want but in this case I need to bind each
> workers and let services knows about them where I want the inverse:
> services notify workers they exist.
>
Hum I should be tired, PUSH/PULL works as expected. Now the on
Hi Benoit,
> I would like to use zeromq as a way to send quick notify workers about
> new tasks and I currently hesitate about the strategy to use.
Have you read the Guide (http://zguide.zeromq.org/)? There are a
bunch of routing examples, particularly in Chapter 3, which should
help you.
-Piet
Hi all,
I would like to use zeromq as a way to send quick notify workers about
new tasks and I currently hesitate about the strategy to use.
Context: I've a server web that forks on all cpus. Each workers can
send tasks to different services. Behind That I want to add or remove
any services I wan
ZeroMQ Guys,
I have a problem that seems to only effect Ubuntu 10.04.1. If you look at the
gist: https://gist.github.com/634738 -- and you can even delete the lines 69
through 94, you'll get an error on line 68 - the call to connect() on Ubuntu.
But on CentOS, it's fine - no error.
I'm using
On Mon, Jan 24, 2011 at 9:22 PM, Michael Kogan
wrote:
> Is it possible for 2 devices to be started with the same socket? I would
> think not, but would like to find out for certain.
>
They can connect, but you'll get a bind error if you try to bind to the same
socket twice, zmq_bind will chuck an
Is it possible for 2 devices to be started with the same socket? I would think
not, but would like to find out for certain.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Hi Oleg,
Thanks for the new examples and updates to the other three; all
changes are now in the zguide repository.
-
Pieter Hintjens
iMatix
On Mon, Jan 24, 2011 at 4:19 PM, Oleg Sidorov wrote:
> Hi.
> I've translated msreader and mspoller examples to ruby.
> Here it is:
> https://github.com/4
Hi.
I've translated msreader and mspoller examples to ruby.
Here it is:
https://github.com/4pcbr/zmq-ruby/blob/master/msreader.rb
https://github.com/4pcbr/zmq-ruby/blob/master/mspoller.rb
Thanks for comments last time!
___
zeromq-dev mailing list
z
Hi All,
Blocking behavior of zmq_term is very good for correctly flushing all
the messages on termination for network connections. However it seems
that this doesn't work so good currently for inproc connections.
For inproc connections with blocking socket.recv() zmq_term might
generate TERM
Hi All,
Blocking behavior of zmq_term is very good for correctly flushing all
the messages on termination for network connections. However it seems
that this doesn't work so good currently for inproc connections.
For inproc connections with blocking socket.recv() zmq_term might
generate TERM o
On 24 January 2011 01:06, Yusuf Simonson wrote:
> Hi,
>
> I'm trying to build a pub/sub engine on top of jzmq for performing
> distributed computation in cloud environments. Systems have a relatively
> high chance of failure, so I want to ensure reliability.
>
> I was wondering if there was any a
I will be out of office for customer meeting from Jan 24th to Jan 31st. During
those days, I only have limited network and phone access. If any urgent case,
please reach me via Tuxedo visitor phone number.
Thanks & Regards,
Leo
___
zeromq-dev mailing l
Hi All,
Blocking behavior of zmq_term is very good for correctly flushing all
the messages on termination for over network connections. However it
seems not so good for inproc connections.
For inproc connections with blocking socket.recv() zmq_term might
generate TERM on our blocking recv earl
On Mon, Jan 24, 2011 at 1:06 AM, Yusuf Simonson wrote:
> I'm trying to build a pub/sub engine on top of jzmq for performing
> distributed computation in cloud environments. Systems have a relatively
> high chance of failure, so I want to ensure reliability.
First of all, do read the Guide and wo
Hi Yusuf,
> By
> reliable, I mean that I want the engine to be resilient to individual
> system failure. So if process P publishes an event with a channel that
> process Q is subscribed to, and Q dies before it finishes processing the
> event, then P should persist the event. At some point in tim
21 matches
Mail list logo
