Received: with LISTAR (v1.0.0; list gopher); Mon, 08 Jan 2001 01:12:30 -0600 (CST) Return-Path: Delivered-To: gopher@complete.org Received: from alexanderwohl.complete.org (localhost [127.0.0.1]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id D12323B807; Mon, 8 Jan 2001 01:12:29 -0600 (CST) Received: by alexanderwohl.complete.org (Postfix, from userid 1000) id BAC04F244; Mon, 8 Jan 2001 02:03:11 -0500 (EST) To: emanuel at heatdeath organisation Cc: gopher@complete.org Subject: [gopher] Re: Gopher server-side programming References: <20010107211343.C31887@success-info.com> From: John Goerzen Date: 08 Jan 2001 02:03:11 -0500 In-Reply-To: <20010107211343.C31887@success-info.com> Message-ID: <87g0iuil00.fsf@complete.org> Lines: 14 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 51 X-listar-version: Listar 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 X-list: gopher emanuel at heatdeath organisation writes: > I know UMN gopherd lets you run shell scripts, kind of like CGI, but > when I played with it, it was quite limited. The other way I've seen is > by modifying the source of the server. You can also write custom programs that listen on a special port (perhaps out of inetd). Because gopher protocol is so simple, there should be no problem doing that. -- John Goerzen www.complete.org Sr. Software Developer, Progeny Linux Systems, Inc. www.progenylinux.com #include