Re: Who can express URL syntax with BNF
montulli@stat1.cc.ukans.edu (Lou Montulli)
Errors-To: listmaster@www0.cern.ch
Date: Mon, 25 Apr 1994 20:50:03 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9404251846.AA41232@stat1.cc.ukans.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: montulli@stat1.cc.ukans.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: montulli@stat1.cc.ukans.edu (Lou Montulli)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Who can express URL syntax with BNF
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: ELM [version 2.3 PL2]
X-Mailer: ELM [version 2.3 PL2]
>
> Anyway... the way to disambiguate is to tell the client to give you
> more info in the path. For example, have the client send:
>
> GET /1234/textsearch?Name%20foo HTTP/1.0
> GET /1234/spacejump?777,888 HTTP/1.0
>
> Hmmm... actually, I think you've found a real problem: what if
> somebody wants to put both types of queries in one document? e.g. what
> if a node has both <ISINDEX> and <IMG ISMAP>, and the user enters
> "777,88" in the search text area? (Forms is not so much of a problem:
> you can put ACTION="/disambiguating/path" and give the server enough
> info to decide it's a form).
>
> It seems that this actually does need to be part of the protocol, and
> not just an application-specific use of the protocol.
>
In this case they should use:
<ISINDEX action="SOME_URL">
and
<a href="SOME_OTHER_URL"><IMG ISMAP></a>
Since you can use seperate url's you can encode the specifics of the
operation in the URL even though the same CGI-BIN script is called.
:lou
--
Montulli@ukanaix.cc.ukans.edu
913/864-0436
University of Kansas
Lawrence, KS 66045 USA