Received: with ECARTIS (v1.0.0; list gopher); Sun, 23 Dec 2007 18:39:47 -0600 (CST) Received: from ms-smtp-02.nyroc.rr.com ([24.24.2.56]) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1J6bM7-0000mL-Eh for gopher@complete.org; Sun, 23 Dec 2007 18:39:46 -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 lBO0cpDv009299 for <gopher@complete.org>; Sun, 23 Dec 2007 19:38:51 -0500 (EST) Message-ID: <02a701c845c5$58f73910$6901a8c0@YTHERIX> From: "Trevor" <greendragon@stny.rr.com> To: <gopher@complete.org> References: <20071223234049.GA10710@pongonova.net> Subject: [gopher] Re: Final dot required on server request? Date: Sun, 23 Dec 2007 19:20:37 -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 071223-0, 12/23/2007), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Status: No (score 0.0): AWL=0.000 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Sun, 23 Dec 2007 18:39:46 -0600 X-archive-position: 1766 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: <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

that's really odd. nearly every gopher server i've connected to stays with the RFC, which indicates the terminating dot is required.

however, gopher is a connectionless protocol. you connect, the server sends and disconnects. so i suppose technically, you don't need the ending period, you just need to read the socket until the connection closes.

trevor

----- Original Message ----- From: <brian@pongonova.net> To: <gopher@complete.org> Sent: Sunday, December 23, 2007 6:40 PM Subject: [gopher] Final dot required on server request?

>I noticed that PyGopherd does not appear to send a final "." character > prior to terminating the connection, but Bucktooth does. A quick read > of the RFC leads me to believe the "." is to be expected. Has this > been deprecated? It's not a big deal, just need to know how to write > a bit of code to either expect or not expect the dot. > > --Brian >