Received: with ECARTIS (v1.0.0; list gopher); Mon, 12 Nov 2007 00:24:35 -0600 (CST) Received: from ms-smtp-02.nyroc.rr.com ([24.24.2.56]) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1IrSim-0005BX-8P for gopher@complete.org; Mon, 12 Nov 2007 00:24:35 -0600 Received: from YTHERIX (cpe-69-205-146-123.stny.res.rr.com [69.205.146.123]) by ms-smtp-02.nyroc.rr.com (8.13.6/8.13.6) with SMTP id lAC6OCD6007082 for ; Mon, 12 Nov 2007 01:24:14 -0500 (EST) Message-ID: <004801c824f4$a6c4e1c0$6501a8c0@YTHERIX> From: "Trevor" To: References: <200711120344.lAC3iR74004902@floodgap.com> Subject: [gopher] Re: GOPHER file format. Date: Mon, 12 Nov 2007 01:19:02 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Antivirus: avast! (VPS 071111-1, 11/11/2007), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Status: No (score 0.0): none X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Mon, 12 Nov 2007 00:24:35 -0600 X-archive-position: 1721 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: greendragon@stny.rr.com 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 as an aside, i've found nothing in the rfc archives that indicates a standard on how servers need to organize their entries, just what data has to be sent. if anyone has info on that, i'd appreciate it. not only am i working on a gopher client for windows, i'd like to build a server as well, since gopher hasn't been a supported (and obscure) option for IIS since windows NT server 4.0 i'd like to put together not only a client for the latest versions of windoze, but have been considering building a server as well. i think the community is severely missing both. and no offense, but i don't want to have to run cygwin or have perl installed to run a gopher server. i'd love to build a native windoze server. anyone who wants to help, let me know. also, i'm having problems linking with the cso lookup types. anyone know where i can find a cso server? NASA used to have one, but it's down, and when i wrote them about it they kind of laughed at me. ("why are you using old technology??") on the up side. a windoze native client is progressing nicely. hopefully i'll have it done soon. keep in mind i have many other projects going on as well. but soon. trevor ----- Original Message ----- From: "Cameron Kaiser" To: Sent: Sunday, November 11, 2007 10:44 PM Subject: [gopher] Re: GOPHER file format. >> It is anything like universal gopher file format ? >> In the HTTP world i can use the *same* html document on any HTTP >> server without problem. And what abbout GOPHER ? >> >> It is any universal form or its always depend on gopher sever ? >> In exampe on SDF's gopherd when i wish to create link to files, I >> must(?) use .links files with contents like: >> >> Name=BIO >> Type=0 >> Path=./bio.txt >> Numb=1 >> >> It is a standard and universal way ? > > This is the UMN links style, which is the most common format, and is > supported > in pygopherd as well. > > Bucktooth does not support it, and some other newer servers might not. The > reason Bucktooth doesn't is simply because I think the format sucked, but > I > do freely admit this wasn't nice for compatibility. > > -- > ------------------------------------ personal: > http://www.cameronkaiser.com/ -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * > ckaiser@floodgap.com > -- It is one thing to praise discipline, and another to submit to > it.-Cervantes >