Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Jul 2002 11:46:50 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from christoph.complete.org (christoph.complete.org [10.201.0.200]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "christoph.complete.org", Issuer "John Goerzen -- Root CA" (verified OK)) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 5AE023B869; Mon, 15 Jul 2002 11:46:46 -0500 (EST) Received: by christoph.complete.org (Postfix, from userid 1000) id B5AF31321E; Mon, 15 Jul 2002 11:46:44 -0500 (EST) Date: Mon, 15 Jul 2002 11:46:44 -0500 From: John Goerzen To: gopher@complete.org, cleeker@gmx.net Subject: [gopher] Re: Hello all Message-ID: <20020715164644.GD3245@complete.org> References: <3D32496A.3040601@gmx.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D32496A.3040601@gmx.net> User-Agent: Mutt/1.4i Content-Transfer-Encoding: 8bit X-archive-position: 641 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Mon, Jul 15, 2002 at 12:02:50AM -0400, Robert Warning wrote: > > Im kinda new to gopher, but after cruising the net I stumbled across > this little gem which is perfect for my needs. (A text only site that Hello Robert, I am glad you found Gopher and dropped by. Let me try to answer your questions: > gives info and downloads on a flashy php-based web tingy im working on, > ironic no) I have a couple questions though. Since gopher is a one way > street from server to client (except for client page requests) how is > cgi handled more specifically these mole things they talk about at Gopher does not have a CGI algorithm as such. Bucktooth "moles" or PyGopherd PYGs both provide for dynamic document and menu generation. Essentially, it is possible to generate documents on the fly, with arbitrary menus, and let the user select things from them. After all, it's just a different select. It works similar to the GET method for CGIs. Take a look at gopher://gopher.quux.org:70/1/pygfarm/dict.pyg for an example. The source to this comes with the pygopherd distribution. It provides a Gopher interface to a DICT server, generating all pages (including that main one) on the fly based on the DICT responses. > bucktooth? What are ASKs and how do they work? What is the differnece ASK blocks are a feature of gopher+ that are similar in concept to HTML forms, but less advanced. They have never been widely implemented or used. > between gopher+ and regular old gopher? Any help would be appreciated. Gopher+ represents extensions to the Gopher protocol that allow MIME types of files, file sizes, multiple views of files, and arbitrary attributes (ie, an abstract). As far as I know, Gopher+ is implemented on the server side only in UMN gopherd and pygopherd, though I think Ralph might have some hacks to bucktooth to do that with that server as well. Gopher+ support on the client side is also somewhat meagre; AFAIK, only UMN Gopher supports it. Pygopherd does automatic gopher+ attribute translation for older clients or HTTP clients, so that they can still view a page reasonably well. -- John -- John Goerzen GPG: 0x8A1D9A1F www.complete.org