Received: with ECARTIS (v1.0.0; list gopher); Sat, 06 Apr 2002 12:53:04 -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 A28523B80D for <gopher@complete.org>; Sat, 6 Apr 2002 12:53:03 -0500 (EST) Received: from sympatico.ca ([64.228.206.14]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20020406175302.HVDQ25090.tomts13-srv.bellnexxia.net@sympatico.ca> for <gopher@complete.org>; Sat, 6 Apr 2002 12:53:02 -0500 Message-ID: <3CAF3587.E70484E9@sympatico.ca> Date: Sat, 06 Apr 2002 12:51:03 -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: Pygopherd nearing gopherd replacement References: <200204061637.IAA19492@stockholm.ptloma.edu> Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 573 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

> bucktooth (original fork) kludges for this by checking if /foo is executable. > If it is, then it treats somedata as a query always. > > I don't know how Ralph's branch handles this.

I had to put in a bit of code to make sense of all this, because you could have the search data, gopher+ stuff, and a dataflag (presumably in that order). Basically it deals with the number of things, the order, and assumes that dataflag would be 1, gopher+ stuff starts with +,!,$, anything else would be a search, you can only have a dataflag if you have gopher+.

Later on I also assumed that in the gopher+ stuff an attribute would be completely uppercase, while a view has lowercase letters. This is not in the spec, but is the only way (AFAIK) to effectively differentiate them (unless you have a list of the possible views, possible attributes, but that could get messy).