From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4297413ecf2b2eadd4f3595a9f7de428@terzarima.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] tree problem From: Charles Forsyth Date: Thu, 3 May 2007 21:21:36 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-xbzeoaxnvpglvydfwusxodlcyf" Topicbox-Message-UUID: 579e094e-ead2-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-xbzeoaxnvpglvydfwusxodlcyf Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i think that for unusual servers, including filters, it's easier just to serve the protocol, rather than try to second-guess an otherwise helpful library. --upas-xbzeoaxnvpglvydfwusxodlcyf Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by lavoro; Thu May 3 18:31:10 BST 2007 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id DFE58634CC for ; Thu, 3 May 2007 13:30:19 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id A6B10632A7 for <9fans@cse.psu.edu>; Thu, 3 May 2007 13:29:40 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29991-01-2 for <9fans@cse.psu.edu>; Thu, 3 May 2007 13:29:40 -0400 (EDT) Received: from smtp.vitanuova.com (host217-34-29-141.in-addr.btopenworld.com [217.34.29.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 7D1F3632A0 for <9fans@cse.psu.edu>; Thu, 3 May 2007 13:29:39 -0400 (EDT) Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] tree problem Date: Thu, 3 May 2007 18:30:19 +0100 From: rog@vitanuova.com In-Reply-To: <599f06db0705030925h57ec834dx56a694a2d82f0e1c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu Errors-To: 9fans-bounces+forsyth=terzarima.net@cse.psu.edu > I want each clunk, not the last one... there will be at most one clunk for an open file, as it's illegal to clone an open fid. in the usual case (when clients are being non-malicious) destroyfid on an open file will be trigged by that clunk. it does seem a pity that there seems to be no way of delaying the response to a clunk without stopping the server read loop. --upas-xbzeoaxnvpglvydfwusxodlcyf--