Received: with ECARTIS (v1.0.0; list gopher); Tue, 14 Oct 2003 08:24:38 -0500 (CDT) Return-Path: <hardburn@runbox.com> X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by gesundheit.complete.org (Postfix) with ESMTP id 0A0301832079 for <gopher@complete.org>; Tue, 14 Oct 2003 08:24:38 -0500 (CDT) Received: from aibo.runbox.com (aibo.runbox.com [193.71.199.94]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by gesundheit.complete.org (Postfix) with ESMTP id 306611832045 for <gopher@complete.org>; Tue, 14 Oct 2003 08:24:37 -0500 (CDT) Received: from [10.9.9.15] (helo=odie.runbox.com) by lufsen.runbox.com with esmtp (Exim 4.20) id 1A9P8h-0006Bo-Kn for gopher@complete.org; Tue, 14 Oct 2003 15:23:03 +0200 Received: from mail by odie.runbox.com with local (Exim 4.20) id 1A9P8V-0000Fm-50 for gopher@complete.org; Tue, 14 Oct 2003 15:22:51 +0200 Content-type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: "Timm Murray" <hardburn@runbox.com> To: gopher@complete.org Subject: [gopher] Re: type-question Date: Tue, 14 Oct 2003 13:22:51 GMT X-Sender: 79977 X-Mailer: RMM Message-Id: <E1A9P8V-0000Fm-50@odie.runbox.com> X-Sender: unknown X-Scanned-By: clamscan at complete.org X-archive-position: 831 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: hardburn@runbox.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

> Hi there, >=20 > I have a small question regarding type 4, 5 and 6 in the gopherprotocol. > First of all I know the use of those types is not recommended (use 9 > instead), but still I have a small question: > Are the type 4, 5 and 6 being sent as 'normal' binary transfers or are th= ey > sent in a different way? So is it different for the client or is it only = the > type declaration of the server (4 or 9, etc) which matters?

According to RFC 1436, only types 9 and 5 are sent in binary (see the Appen= dix,=20 heading 'Binary file Transaction'). Really, there are a bunch of other=20 types that need to be sent in binary form. Issues like these are better ad= dressed=20 in Gopher+.