Re: Annoucement: Local Browser Execution

Tony Sanders <sanders@BSDI.COM>
Errors-To: sanders@BSDI.COM
Errors-To: sanders@BSDI.COM
Message-id: <199312140552.XAA02630@austin.BSDI.COM>
Subject: Re: Annoucement: Local Browser Execution 
In-Reply-To: George Phillips's message of Mon, 13 Dec 1993 17:36:07 PST.
Errors-To: sanders@BSDI.COM
Organization: Berkeley Software Design, Inc.
Date: Mon, 13 Dec 1993 23:52:40 -0600
From: Tony Sanders <sanders@BSDI.COM>
Content-Length: 680
> I've been working on a new URL scheme called "x-exec:" which directs
> One last thing.  I'm certainly interested in discussing viable
> alternatives to x-exec: and suggestions for improving it.  Flames
> about it being "a bad thing" and/or "the wrong thing" will be
> accepted in the same cheerful spirit as Mosaic Motif flames.

Ok, define a content type application/x-exec that returns some data for
you to deal with.  This doesn't require *ANY* changes to the browser and
at some point down the road you will be able to authenticate the data
instead of being forced to trust just anyone.  Same effect, much more
flexible, and it doesn't clutter the URL space.