Re: Annoucement: Local Browser Execution

• Mail folder: WWW Talk Oct 93-present
• Next message: Kevin 'Kev' Hughes: "Re: Web posting policy"
• Previous message: George Phillips: "Re: Annoucement: Local Browser Execution "
• In-reply-to: Tony Sanders: "Re: Annoucement: Local Browser Execution "

Date: 13 Dec 93 23:22 -0800
From: George Phillips <phillips@cs.ubc.ca>
To: <www-talk@nxoc01.cern.ch>
Cc: <www-talk@www0.cern.ch>
In-reply-to: <199312140552.XAA02630@austin.BSDI.COM>
Message-id: <7053*phillips@cs.ubc.ca>
Subject: Re: Annoucement: Local Browser Execution 

Tony says:
>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.

As near as I can tell with Mosaic, you'd still have to make some
changes.  Unless the content type is text/html, it just doesn't
get displayed on the document window.  Even so, I think you're still
a far stretch from having the same effect as x-exec.  For instance,
you need at least a server to drop these application/x-exec
documents on the browser.

I could be wrong, but I certainly can't figure out how to replace
x-exec: with application/x-exec.  If you know how, please show
me.