Message-id management revisited

Mark Taylor m.b.taylor at bristol.ac.uk
Tue Jun 10 09:35:41 PDT 2008


On Mon, 9 Jun 2008, Luigi Paioro wrote:

> My 2 cents again: I vote 9.

this sounds like consensus then.  Thomas, could you regenerate the 
Synchronous and Asynchronous Call/Response cartoons to reflect the
change:


    Synchronous (just changes of some param names):

       Sender                      Hub                        Recipient
       ------                      ---                        ---------
               ----------->                   ----------->
           response = callAndWait()        receiveCall(msg-id)

                                              <----------
                                           reply(msg-id)

    Asynchronous:

       Sender                      Hub                        Recipient
       ------                      ---                        ---------
           (1)------------>              (2)-------------->
                    call(msg-tag)         receiveCall(msg-id)

              <-----------(3)               <-------------(4)
           receiveResonse(msg-tag)        reply(msg-id)

Possibly (1) in the asynch case should be labelled "msg-id = call(msg-tag)",
since that's what happens, but in most cases the msg-id will be ignored,
so I'd say it's probably best to do it as illustrated above for clarity.
But whichever you think best.

thanks

Mark

-- 
Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
m.b.taylor at bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/



More information about the apps-samp mailing list