Re: Annoucement: Local Browser Execution

• Mail folder: WWW Talk Oct 93-present
• Next message: Tim Berners-Lee: "WWW and EDI: The need"
• Previous message: Tim Berners-Lee: "EDI and WWW"
• In-reply-to: George Phillips: "Re: Annoucement: Local Browser Execution "

To: phillips@cs.ubc.ca
Cc: www-talk@nxoc01.cern.ch
In-reply-to: George Phillips's message of Mon, 13 Dec 1993 23:22:00 -0800 <7053*phillips@cs.ubc.ca>
Subject: Re: Annoucement: Local Browser Execution 
From: Larry Masinter <masinter@parc.xerox.com>
Sender: Larry Masinter <masinter@parc.xerox.com>
Fake-Sender: masinter@parc.xerox.com
Message-id: <93Dec15.013323pst.2732@golden.parc.xerox.com>
Date: 	Wed, 15 Dec 1993 01:33:13 PST

I think x-exec: is an ugly hack. I'm about to propose something that
at first glance looks like an uglier hack, but maybe after you think
about it for a bit you won't shoot me:

Right now, you're taking something 'x-exec:blah blah' and treating it
as a URL that executes something special.

Why not, instead of searching for "x-exec:", search for
"http://cs.ubc.ca/exec/".  That is, build *into your client* the
special case that if you see "http://cs.ucb.ca/exec/blah blah",
instead of sending http protocol somewhere, you execute "blah blah" as
a shell command.

This doesn't clutter the URL space either. You might think it is
rather special purpose to put such an odd special case in your
software, but in fact it is fairly general. 

#define DUMMY_HTTP_EXEC_SERVER "cs.ucb.ca"

if you like.

You'll get all the features you wanted with x-exec, and you'll also
get pages that function when you browse them with clients that don't
have any special purpose extensions.