Hi Romano, > Is this what you want? > > - client send a request to the server port and ask for an anwer on a given > port > - client go to wait on his port > - server awakes for the client request and makes what the request asked > - server send an answer to the client port > - server wait > - client awakes because receveis the answer > > So the "ticket" should be only a client port to wait for. > > This is the mode in which async code was executed by ARexx on old Amiga.
That looks pretty elegant. It confirms (in my mind) that in async-io the site (function/port/ticket) of the receipt is different from where on the client the request originated. I don't know what the features/consequences are for the different implementation strategies - so I leave to Maarten and others to work out what the implementation should be. Thanks! Brett. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
