From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] changing file ownership with fossil? In-Reply-To: Your message of "Wed, 15 Oct 2003 06:43:01 BST." From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21921.1066227917.1@t40.swtch.com> Message-Id: Date: Wed, 15 Oct 2003 10:25:17 -0400 Topicbox-Message-UUID: 6f4db036-eacc-11e9-9e20-41e7f4b1d025 > i was also trying to decide whether the database > was really needed. without the database you only have two pieces of information per file -- the mtime/length on the local system and the mtime/length on the remote system. a comparison between these two can only have two outcomes, whereas there are three outcomes in the current system: - file is outdated, needs updating - file is fine, no updating - file is outdated but locally changed, warn user by storing a complete history of files given out on the server, you could avoid storing the local information, but that requires the server knowing more about its clients than it currently does. right now the per-client data is all on the clients, and the server is "stateless" as it were. (the database on the server could be removed if you redefine mtime on directories properly.)