Mime-Version: 1.0
Message-Id: <p05010404b8beb412dd09@[205.189.158.32]>
In-Reply-To: <DC4522A8-3C47-11D6-B325-0003930BF072@complete.org>
References: <DC4522A8-3C47-11D6-B325-0003930BF072@complete.org>
Date: Wed, 20 Mar 2002 16:51:02 -0500
To: gopher@complete.org
From: Robert Hahn <rhahn@tenletters.com>
Subject: [gopher] Re: \n.\n
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


John:

I would fully support this if you can explain to me how a gopher 
client is supposed to 'know' when the end of a file is and closes the 
connection.

I don't know much about server design and certainly about this 
implementation (yet), but I do understand that the gopher0 and + spec 
indicated that the reason for \n.\n is to indicate EOF.

thx,
-rh

>I would like to abolish the adding of "." at the end of text gopher
>documents.  Since we have most of the world's gopher client and server
>authors in this group, we can do it :-)
>
>Details:
>
>SERVER:
>
>All gopher servers MUST NOT add a "\n.\n" end-of-file marker to files
>being transmitted.
>
>CLIENT:
>
>All gopher clients MUST NOT remove "\n.\n" from the end of files.
>
>Note: I say this for clients to because we don't want to have to deal
>with the case of having a file that ends with a dot.