Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Apr 2002 16:03:32 -0500 (EST) Return-Path: <rhahn@tenletters.com> Delivered-To: gopher@complete.org Received: from quarry.com (mail.quarry.com [205.189.158.4]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 7FE103B811 for <gopher@complete.org>; Mon, 15 Apr 2002 16:03:32 -0500 (EST) Received: from [205.189.158.32] (205.189.158.32) by quarry.com with ESMTP (Eudora Internet Mail Server 3.0.1) for <gopher@complete.org>; Mon, 15 Apr 2002 17:03:31 -0400 Mime-Version: 1.0 X-Sender: rhahn@mail.quarry.com (Unverified) Message-Id: <p05010407b8e0ee8a1cdc@[205.189.158.32]> In-Reply-To: <20020415205042.ERIN6268.tomts24-srv.bellnexxia.net@[209.226.175.22]> References: <20020415205042.ERIN6268.tomts24-srv.bellnexxia.net@[209.226.175.22]> Date: Mon, 15 Apr 2002 17:04:24 -0400 To: gopher@complete.org From: Robert Hahn <rhahn@tenletters.com> Subject: [gopher] Re: Views Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 590 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: rhahn@tenletters.com 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

If you're open to changing the spec, then perhaps it should be up to the client to specify what's 'preferred'. How can the server know what a client wants, really?

In that case, the harder question to ask is: how can a client tell the server what's preferred?

I don't have the spec handy right now, but can we have it so that clicking 'pyramid' results in the server sending a list of extensions (in the form of a gophermenu) to the client, then the client secretly (w.r.t. the user) re-opening a new request for the preferred format, or, if the client doesn't know, ask the user their preference before opening the second request? IOW, put the intelligence in the client...

Maybe this idea doesn't change the spec...

-rh

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