>
> Hi all,
>
> For those interested in theoretical foundation of 0MQ, I've put down my
> thoughts here:
>
> http://www.250bpm.com/concepts
>
> Martin
Hi Martin,
The paper is great and makes many things clearer. Thank you!
There is one sentence that confuses me, at the top of "Design Principles
Hi, Andrew.
i don't understand what this sort of specification is meant to accomplish.
>
I said I didn't find a better place to post this on zmq website, so posted
it at rfc.zeromq.org. It is simply a too big for an email message. It is
meant to accomplish availability for people to read it.
it
On Tue, Jun 28, 2011 at 12:06 PM, Martin Sustrik wrote:
> On 06/28/2011 05:57 AM, Artur Brugeman wrote:
>
> It's based on XREP sockets now. I've given quite a lot thinking to it,
>> and can share my experience.
>>
>
> Please, do so.
>
> Martin
>
>
> Naive approach would be to allow for explicit acks so that there could
> be at most one request sent to a specific peer at any single moment.
> That would at least allow load-balancer to distinguish "busy" peers from
> "idle" peers and base the load-balancing on that.
>
> However, that doesn't
l ask
questions before making suggestions.
And I now realized that patch doesn't really solve the problem, as
connection establishment is not an atomic operation. So, sorry for
taking your time with this stupid idea.
--
Artur Brugeman
___
Hi, Pieter.
>> Yes, thats right, If you've got a better idea how to solve my problem, I'll
>> be happy to try it.
> A few things come to mind. As Lucas says, this seems close to the
> Freelance pattern so I'd definitely try to use that. There are are
> number of aspects that could be helpful:
>
>
pe=pdf
Plus some more stuff like heartbeats to know who is online.
--
Artur Brugeman
> Hi Artur,
>
> I am a fellow newbie, but I think I see what Pieter was getting at.
>
> Your description seems to match the Freelance Pattern in the guide:
> http://zguide.
Hi Pieter,
Yes, thats right, If you've got a better idea how to solve my problem, I'll be
happy to try it.
Also, there is, probably, another problem with p2p - connections
are not stable, peers come and go. If peer I'm connected to dies, it might not
show up for quite a long time (of even ever).
Hi.
I'm offering a patch which allows us to check whether a certain named pipe
exists at XREP socket. Works this way:
char * identity = ...;
size_t len = strlen (identity);
assert (len > 0);
zmq_getsockopt (socket, ZMQ_PEER_EXISTS, identity, &len);
// len is reset to 0 if such peer exists
if (le
implemented?
Thank you.
Artur Brugeman
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
10 matches
Mail list logo
