Received: with LISTAR (v1.0.0; list gopher); Sat, 12 Jan 2002 14:48:20 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from ns2.tudelft.nl (ns2.tudelft.nl [130.161.180.65]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 871253B81A for ; Sat, 12 Jan 2002 14:48:20 -0500 (EST) Received: from listserv.tudelft.nl (listserv.tudelft.nl [130.161.180.33]) by mailhost1.tudelft.nl (PMDF V6.0-025 #37171) with ESMTP id <0GPU004GXCCJQL@mailhost1.tudelft.nl> for gopher@complete.org; Sat, 12 Jan 2002 20:48:19 +0100 (MET) Received: from mailhost.tudelft.nl (kvz346.kvz.tudelft.nl [130.161.68.146]) by listserv.tudelft.nl (8.10.2+Sun/8.10.2) with SMTP id g0CJmIf11427 for ; Sat, 12 Jan 2002 20:48:19 +0100 (MET) Date: Sat, 12 Jan 2002 20:52:15 +0100 From: Stefan Rieken Subject: [gopher] Re: GopherFS implementation questions In-reply-to: <"from hardburn"@runbox.com> To: gopher@complete.org Message-id: <20020112205215.C3643@Pflipp> MIME-version: 1.0 X-Mailer: Balsa 1.0.pre5 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit References: <87y9j3fqy7.fsf@complete.org> <20020112191546.A3643@Pflipp> X-archive-position: 326 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: StefanRieken@SoftHome.net Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Sat, 12 Jan 2002 19:37:23 Timm Murray wrote: > I've been thinking about having a full-fledged Unix filesystem > over Gopher. Something that would include uids/gids and could be > used as a replacement for NFS. Hmm, this is somewhat the other way around, but is also quite cool. I already see this email thread falling apart into little subthreads now :-) Of course as a server, this would work just OK because you can make up your own filesystem -> gopher policies. So an exported filesystem would be interpretable by all kinds of gopher clients, and additionally a special-purpose "think NFS" client would be able to interpret the data from this "think NFS" server in a "think filesystem" way ...right? It *would* be fairly well doable to implement this "think NFS" client. Actually, all John's and my problems would be gone then. But it would *only* be able to communicate with a special purpose "think NFS" server. Otherwise, all problems are up again... > The nice thing about using Gopher+ as a filesysem is that you can > have full-fledged MIME types, not just relying on the filename > extention. "That is *so* `80's!" My client now mostly resolves MIME stuff by a combination of an "clicked URL history hack" (in which the filetype byte of the directory listing in which was clicked is stored so that when the new URL will be loaded it can be resolved) and "sniffing" the files themselves (using standard GnomeVFS functions). Of course metadata would be better. Extentions suck. I was wondering: according to the Gopher+ specification, one file could be available in different mime type versions, but listed only once in the dirlisting. Does this happen in practice? Greets, Stefan -- "'Abnormal Psychology'. Are you a doctor, mr. Murdock?" "Uh, no ma'am, I'm insane."