Received: with LISTAR (v1.0.0; list gopher); Mon, 11 Feb 2002 16:35:26 -0500 (EST) Return-Path: <sugaku@sympatico.ca> Delivered-To: gopher@complete.org Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id D390D3B8AB for <gopher@complete.org>; Mon, 11 Feb 2002 16:35:25 -0500 (EST) Received: from sympatico.ca ([64.228.192.69]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020211213524.FXLK3415.tomts13-srv.bellnexxia.net@sympatico.ca> for <gopher@complete.org>; Mon, 11 Feb 2002 16:35:24 -0500 Message-ID: <3C6838E2.C2902027@sympatico.ca> Date: Mon, 11 Feb 2002 16:34:26 -0500 From: Ralph Furmaniak <sugaku@sympatico.ca> X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: gopher@complete.org Subject: [gopher] Re: Gopher wishlist References: <3C682904.BF4BE07D@sympatico.ca> <20020211161035.A28611@mothra.dyndns.org> Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 426 X-listar-version: Listar 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:listar@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Listar version 1.0.0 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

All good points. Lets clear up what makes gopher gopher, and not just an http wannabee. Some of the main things (distinctions) are that gopher presents strict text menus, and each line is either text, or a single link (ie, no single word linking as this can get messy).

Yes, we should add things to fix problems and not for the coolness factor, and that is why we want people talking about what they like and dislike.

I do not quite agree about backwards compatability. Gopher+ was designed to be backwards compatible, but if you look you'll see that the client request specifically signals whether it be gopher0 or gopher+, and the server sends back different data depending. umn gopher client (AFAIK) always sends a '$' request to the server, and the umn server then sends back something that would cause a gopher0 client to choke and die.

So similarly, we can add new things that a client can request. I'm not really sure what things can be done, but other people should have some ideas.

What could be put into the header/metadata? I don't know. I'm sure many people would be against implementing cookies <g>. There could be a title included (might be some benefits, might not. depends on the client), and maybe a content-type. I guess there isn't much use; gopher already has sufficient capabilities.