Re: HTTP problem or Mosaic problem?

• Mail folder: WWW Talk Apr 94-present
• Next message: Tim Berners-Lee: "Real-time movies and libwww"
• Previous message: Larry Masinter: "Re: HTTP problem or Mosaic problem?"
• Maybe in reply to: Larry Masinter: "Re: HTTP problem or Mosaic problem?"
• Reply: Jon P. Knight: "Re: HTTP problem or Mosaic problem?"

Errors-To: listmaster@www0.cern.ch
Date: Wed, 15 Jun 1994 12:12:07 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <94Jun15.030852pdt.2760@golden.parc.xerox.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: masinter@parc.xerox.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Larry Masinter <masinter@parc.xerox.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: HTTP problem or Mosaic problem?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

I suggested setting up:
	application/x-mcast-session
to be `a text file with a list of address/port descriptions for multicast
audio and video'.

and Jon P. Knight replied:

> Or use the MIME type application/x-csh along with vsafecsh to launch the
> applications using a small script supplied by the server.  Check out
> Anders Klemets Media on Demand Server to see how it works:

> 	http://www.it.kth.se/~klemets/vatplay.html

> By using vsafecsh you limit the danger of naught people running dubious
> scripts on your machine.

> Jon

but I like setting up a new MIME type for mcast-session because it is
nominally less operating-system dependent than a `x-csh' type.

Oh, I suppose one could do a 'vsafecsh' for Windows that actually only
special cases a couple of shell commands, but it seems wrong to load
it all into one media type.