Hi,
instead of sending only the pid in the request to protocol B, you can
pass further information and send them back in the reply.
We do this in our transactional key-value store Scalaris, which is
written in Erlang, to ease use of asynchronous protocols
stacks. (scalaris.googlecode.com). There
Hi,
Thank you for your responses.
I think I did not write my question clearly enough. I'm sorry for that.
I have no API. I'm starting from scratch.
My question is about how to implement some bare asynchronous protocols that
call subprotocols.
For example have a look at this article:
http://www.sho
I'm not sure exactly what layer you're talking about, but I'm going to
assume you mean the API itself. Generally in any asynchronous API, you need
to have some object that represents the current state of the protocol state
machine, and that either needs to be passed in as an argument (generally
the
On 6/09/13 10:33 AM, realcr wrote:
Hi,
I was reading recently some information about asynchronous protocols
(For example byzantine agreement, reliable broadcast and some more). I
noticed that there are many articles about these subjects, some date
back to year 2000, though I haven't found any exa
Hi,
I was reading recently some information about asynchronous protocols (For
example byzantine agreement, reliable broadcast and some more). I noticed
that there are many articles about these subjects, some date back to year
2000, though I haven't found any examples of making such code work.
I re
