From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3EC968C4.9000006@ameritech.net>
From: northern snowfall <dbailey27@ameritech.net>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Channel casting
References: <3100726675a9ffcb9f2eefc78956dba1@plan9.bell-labs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 19 May 2003 18:29:08 -0500
Topicbox-Message-UUID: b3d0fe08-eacb-11e9-9e20-41e7f4b1d025

>
>
>For the case you describe, the client typically
>sends a (request, return-channel) pair and
>then recvs from the return channel, which is
>private to that client.
>
Ah, okay. Let me make sure I understand this.
First, client C creates its own Channel.

Second, C generates the request structure
suitable to the server thread, including the private
Channel as a member.

Third, C sends the request structure to to the
server S via the public Channel.

Fourth, S retrieves said req, manifests the proper
response structure, then sends the response back on
C's private Channel.

Finally, C receives the response on the private channel,
then, optionally closes the private chan.

Correct?

>