Subject: [gopher] Re: Getting file info from an URI??
From: Stefan Rieken <StefanRieken@SoftHome.net>
To: gopher@complete.org
In-Reply-To: <200106151437.HAA12236@stockholm.ptloma.edu>
References: <200106151437.HAA12236@stockholm.ptloma.edu>
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Date: 15 Jun 2001 17:37:17 +0200
Message-Id: <992619438.769.0.camel@Pflipp>
Mime-Version: 1.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


On 15 Jun 2001 07:37:50 -0700, Cameron Kaiser wrote:

> Well, this isn't *really* true. The first character is always the item type.

Well, that may be common current practice, but that's not quite required
behaviour from either the Gopher or the Gopher+-standards, is it?

If so, determining the file type by looking at the first character may
now work in 99% of the cases, until someone develops a "new, improved"
Gopher server which uses different selectors that gets popular, after
which maybe only in 70% of the cases this will work.

> True; a Mac HFS gopher server, of which there are some, uses ":".

Makes me wonder: how do webbrowsers translate these server's selector to
an URI? Does it leave in the ":" or replace it with a "/"? Just curious.

Greets,

Stefan
--
"The main problem is getting something that works without crashing the
NT/ 2000 client" -- Jeremy Allison, Samba development team