[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[gopher] Re: Getting file info from an URI??

> Now the Gopher standard writes: "[t]he selector string should mean
> nothing to the client software; it should never be modified by the
> client." Now this implies three things: first, one _cannot_ determine a
> file type by looking at the format of an URI.

Well, this isn't *really* true. The first character is always the item type.
Some gophers like URLs in this form


and others (like Bucktooth) don't need it twice,


but you can always make some guesses from that leading first character and
except for the I item type which is usually but not always image/jpeg most
of the others match up fine with a single MIME type. In fact, in the gopher
browser I'm working on for the C64, it turns item types back into MIME
types internally so the same handlers can do the same operations.

> Second, one _cannot_
> assume that a Gopher selector is seperated by slashes.

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

> And third, even
> if one could do just that, one _cannot_ assume that a "parent directory"
> lists the child.

Probably not.

> 1) Use the Gopher+ "!" (information) selector feature
>    Problem: requires Gopher+. Can one assume Gopher+ nowadays?
>    Or are there still many "non-plus" Gopher servers around?
>    Please comment on this.

No, there are many "G-" servers, including mine.

----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- Why, I'd horsewhip you if I had a horse! -- Groucho Marx -------------------

Reply to: