From: Cameron Kaiser <spectre@stockholm.ptloma.edu>
Message-Id: <200203210216.SAA14978@stockholm.ptloma.edu>
Subject: [gopher] Re: The road ahead
In-Reply-To: <p05010405b8beb4cc08ab@[205.189.158.32]> from Robert Hahn at "Mar
 20, 2 05:22:25 pm"
To: gopher@complete.org
Date: Wed, 20 Mar 2002 18:16:05 -0800 (PST)
Cc: gopher@complete.org
MIME-Version: 1.0
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


> One recurring issue on the lists is about how you mix gopher links 
> with copy.  It's my impression that the standard doesn't allow the 
> info type to begin with, let alone the mixing of the two.  I would 
> like to suggest that we handle this in a more formal and fluid 
> manner. What I'd like to see done is to remove the content-length 
> restriction of each block of data, and to allow newlines so that we 
> can create paragraphs of text without requiring multiple 
> url/mimetype/language/bytesize declarations...

Do you mean in the protocol or in the gopher menu definitions?

If you mean in the menu files, bucktooth already has a streamlined format
for this that more or less groks what is and isn't text copy.

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- All wiyht. Rho sritched mg kegcaps awound? ---------------------------------