Complete.Org: Mailing Lists: Archives: gopher: April 2002:
[gopher] Re: Views
Home

[gopher] Re: Views

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Views
From: Ralph Furmaniak <sugaku@xxxxxxxxxxxx>
Date: Mon, 15 Apr 2002 16:50:42 EDT
Reply-to: gopher@xxxxxxxxxxxx

> Not only that, but it doesn't document all of the options even.  The 
> best bet is the source code -- see gopherd/gopherd.c and 
> object/GSgopherobj.c for starters.

Then it looks like I just got the bare-bones <g>

> I like it!  How do you define which view is the default, though?  (In 
> Gopher+ parlance, the "preferred" view)

Currently there is no way to change the order, it's just simple FIFO.  Doesn't 
the umn client choose it's own default?

Any suggestions on how to do this?  You could put it into one of the special 
config files.  Or you could prepend/append something to the filename.  
Prepending a number will already work since it is alphabetic, and the actual 
filename of the request does not matter much.


Does anyone think gopher+ should be changed in this respect? In the previous 
example gopher+ clients would see `pyramid` with multiple views.  When someone 
downloads it would it just be called `pyramid`?  The downloaded file would need 
to have an extension, especially if the user downlaods multiple views.  The 
client could try to reverse-engineer the extension, but this still can lead to 
problems.

Including something about the extension would also make it easier for the 
server to find the requested view.



[Prev in Thread] Current Thread [Next in Thread]