To: uri@bunyip.com
Subject: Gopher+ strings
From: Larry Masinter <masinter@parc.xerox.com>
Message-Id: <94Aug13.173940pdt.2761@golden.parc.xerox.com>
Date: Sat, 13 Aug 1994 17:39:26 PDT
After review of what was written against some clarifying messages from
Mark McCahill, I've come to believe that my attempt at 'clarifying'
the Gopher+ selection is incorrect:
================================================================
Suspected text:
================================================================
More explicitly, if the Gopher+ URL refers to a Gopher search type
(that is, if the Gopher type is 7), the client sends to the Gopher
server the Gopher selector string, followed by a tab, followed the
search string, followed by a tab, followed by the Gopher+ commands.
If the Gopher+ URL does _not_ refer to a Gopher search (when the
Gopher type is not 7), the Gopher client sends to the server the
Gopher selector string, followed by a tab, followed by the Gopher+
commands.
================================================================
This is false. What determines whether you send any search string at
all is whether the <search> element is empty.
<URL:gopher://turnip.com/7a_search_engine%09%09+3D_icon>
should send
a_search_engine<tab>+3D_icon
while
<URL:gopher://turnip.com/7a_search_engine%09foo%09+3D_icon>
should send
a_search_engine<tab>foo<tab>+3D_icon