“Jean-Francois Joly” <email@example.com> wrote:
You don’t send messages to channel ids… you send messages to
client - connection → channel - server
Nice, the concept is getting a lot more clearer now…!
This brings me to an another question… ChannelCreate() returns a chid
because it is on the server side. MsgReceive uses this chid but also
returns a receive-id. (Which MsgReply() uses) Why can’t MsgReply use the
chid again instead of the receive-id, whatever that might be? Seems logic
to send back the reply to the channel id, no?
In case of multiple threads, and multiple clients, the received ID really
identifies which client is blocked. For example, if a server receives
requests from 10 different clients, but doesn’t reply to them, the server
will have 10 different receive IDs. When the server does do the MsgReply,
the receive ID identifies which client the server is replying to.
And when you throw in threads on the client side, the argument is even stronger.
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at www.parse.com
Email my initials at parse dot com.