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.shoup.net/papers/abba.ps It describes some algorithm called AVSS, that calls to an algorithm called Asynchronos Broadcast. The point is that AVSS calls Asynchronous Broadcast more than once. I want to create some kind of protocol manager to be able to deal with that, and identify somehow which call is which. (So that messages from the first broadcast won't be accidentally sent to the other broadcast). It is done for educational purposes, I always wanted to know how would it be like to have that pseudo code from the article as some real running code.
I hope it makes things clearer about what I'm asking. Please tell me if more clarification is needed :) Regards, real. <http://www.shoup.net/papers/abba.ps> On Mon, Sep 9, 2013 at 8:04 PM, Sean Lynch <se...@literati.org> wrote: > 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 first) or is implicitly stored in the object you're calling the "handle > message" method on in any OO language. There's no reason for the > implementation to get confused about multiple simultaneous protocol > instances, whether or not those instances are nested. > > > On Fri, Sep 6, 2013 at 12:33 AM, realcr <rea...@gmail.com> 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 examples of making such code work. >> >> I refer you to >> http://www.shoup.net/papers/abba.ps >> for an example of such article. >> >> In this article it seems like the author has the ability to call one >> asynchronous protocol from the execution of another asynchronous protocol, >> Though I could not find any specific explanation to the design of such a >> system. >> >> I will try to be more specific: >> If protocol A calls protocol B twice during its execution, and during the >> second execution of protocol B it sends some message, how does the node on >> the other side of the line know whether the message sent refers to the >> first execution of the B protocol, or to the second one? >> >> I assume some of you had the opportunity to think about these kind of >> challenges. Do you have an idea for a simple solution to resolve this, or >> maybe do you know about an existing implementation? >> >> Regards, >> real. >> >> >> >> _______________________________________________ >> p2p-hackers mailing list >> p2p-hackers@lists.zooko.com >> http://lists.zooko.com/mailman/listinfo/p2p-hackers >> >> > > _______________________________________________ > p2p-hackers mailing list > p2p-hackers@lists.zooko.com > http://lists.zooko.com/mailman/listinfo/p2p-hackers > >
_______________________________________________ p2p-hackers mailing list p2p-hackers@lists.zooko.com http://lists.zooko.com/mailman/listinfo/p2p-hackers
