From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4405D2A2.4040505@lanl.gov>
Date: Wed,  1 Mar 2006 09:58:10 -0700
From: Ronald G Minnich <rminnich@lanl.gov>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 9p and how can I know when a write is finished
References: <3427729765b4e88fb0db2d794e3cdbc6@cat-v.org>
In-Reply-To: <3427729765b4e88fb0db2d794e3cdbc6@cat-v.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 0777647a-ead1-11e9-9d60-3106f5b1d025

uriel@cat-v.org wrote:
>>On Wed, Mar 01, 2006 at 03:29:58PM +0100, Gabriel Diaz wrote:

>>As far as I understood, you wait until Tclunk.
>
> Wrong, the Tclunk is not warranteed to arrive any time soon.
>
> Tclunk != close()


you guys are all confusing me. AFAIK, if you have written a plan 9
server, you have the standard Ye Olde Server Dispatche Functionne.

Said function, when it gets a Req with an op type of Twrite, calls the
appropriate server function, and replies.

I just finished writing another one of these (A GPS server ... fun!) and
it all Just Works.

So, I don't see the problem. Plan 9 packet sizes can be pretty big ---
much much bigger then the MTU on a network -- so the 9p server code
deals with it. When your Twrite gets called, it has the data.

ron