From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 1 Mar 2006 11:31:26 -0500 From: jmk@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] 9p and how can I know when a write is finished In-Reply-To: <3acfc358add926f6e589cb9faaf299fa@vitanuova.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 076c87bc-ead1-11e9-9d60-3106f5b1d025 On Wed Mar 1 10:57:01 EST 2006, forsyth@vitanuova.com wrote: > >>Wrong, the Tclunk is not warranteed to arrive any time soon. > >>Tclunk != close() > > > In the end you are on the safe side when waiting for Tclunk. > > i think it's sad not to implement close [or equivalent] -> Tclunk in a timely way, > and indeed in an orderly manner (wrt the same client process), > at least for files, and especially for files with DMEXCL. The shadowy '9P Dubious Protocol Enhancement Committee' will perhaps consider that at their next secret meeting.