From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <13426df10711010904r317f9fd6v14a87dc2f024b0b1@mail.gmail.com> Date: Thu, 1 Nov 2007 09:04:25 -0700 From: "ron minnich" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] QTCTL? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <317e48249cbfecef84062b5463b65b8d@plan9.bell-labs.com> Topicbox-Message-UUID: e35a1e6e-ead2-11e9-9d60-3106f5b1d025 Why not just have a file that a client reads that lets the client know of changes to files. client opens this server-provided file ("changes"? "dnotify"?) Server agrees to send client info about all FIDS which client has active that are changing. Form of the message? fid[4]offset[8]len[4] It's up to the client to figure out what to do. if the client doesn't care, no extra server overhead. no new T*, no callbacks (which i can tell you are horrible when you get to bigger machines -- having an 'ls' take 30 minutes is no fun). No leases. The fact is we have loose consistency now, we just don't call it that. Anytime you are running a file from a server, you have loose consistency. It works ok in most cases. ron