Received: with ECARTIS (v1.0.0; list gopher);
 Mon, 15 Apr 2002 15:50:43 -0500 (EST)
Return-Path: <sugaku@sympatico.ca>
Delivered-To: gopher@complete.org
Received: from tomts24-srv.bellnexxia.net (tomts24.bellnexxia.net
 [209.226.175.187])
	by pi.glockenspiel.complete.org (Postfix) with ESMTP id 318093B811
	for <gopher@complete.org>; Mon, 15 Apr 2002 15:50:43 -0500 (EST)
Received: from [209.226.175.22] by tomts24-srv.bellnexxia.net
          (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP
          id
 <20020415205042.ERIN6268.tomts24-srv.bellnexxia.net@[209.226.175.22]>
          for <gopher@complete.org>; Mon, 15 Apr 2002 16:50:42 -0400
From: Ralph Furmaniak <sugaku@sympatico.ca>
To: gopher@complete.org
Subject: [gopher] Re: Views
Date: Mon, 15 Apr 2002 16:50:42 EDT
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-Id: 
 <20020415205042.ERIN6268.tomts24-srv.bellnexxia.net@[209.226.175.22]>
X-archive-position: 589
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: sugaku@sympatico.ca
Precedence: bulk
Reply-to: gopher@complete.org
List-help: <mailto:ecartis@complete.org?Subject=help>
List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-ID: Gopher <gopher.complete.org>
X-List-ID: Gopher <gopher.complete.org>
List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe>
List-owner: <mailto:jgoerzen@complete.org>
List-post: <mailto:gopher@complete.org>
List-archive: <http://www.complete.org/mailinglists/archives/>
X-list: gopher


> 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.