Message-ID: <3C45F78E.D30C5EA2@sympatico.ca>
Date: Wed, 16 Jan 2002 16:58:38 -0500
From: Ralph Furmaniak <sugaku@sympatico.ca>
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Gopher+ Protocol Question
References: <3C45F06C.9CB51796@sympatico.ca> <3C45F1EA.476AD88E@sympatico.ca>
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


Yay, now there is also a dataflag to deal with!
What is the format of the datablock as sent by the client?  The information
wasn't too clear about this.  Is it just either "-1", "-2", or number of bytes
followed by CRLF followed by the data?

Ralph Furmaniak wrote:

> Scratch that, this is what a gopher+ guide said, but the official protocol
> says otherwise.  So if after the selector there is a tab and something, if
> it starts with one of +,!,$ it is gopher+, otherwise it is a search
> string.  Do clients ever send an empty search string, then the gopher+
> stuff?
>
> Ralph Furmaniak wrote:
>
> > >From what I read, Gopher+ clients should send after the selector
> > "F[search string]F[gopher+ stuff]" so that you can tell these two
> > apart.  Is this always the case, ie is it fine to just split the string
> > between tabs and use them, or should I check to make sure that [search
> > string] is not actually the gopher+ string?