[5060] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: Waiting for HTML+ for executing LOCAL (serverless) scripts??

daemon@ATHENA.MIT.EDU (wmperry@spry.com)
Tue Aug 2 12:15:25 1994

Date: Tue, 2 Aug 1994 18:00:35 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: wmperry@spry.com
From: wmperry@spry.com
To: Multiple recipients of list <www-talk@www0.cern.ch>

Rick Troth writes:
>Bill Perry writes:
>>    Basic syntax is
>> 
>> x-exec://progname/foo/bar/baz?blort
>> 
>>    progname will be looked for in 'trusted' directories on your local
>> machine - no explicit paths are allowed.  (So no x-exec://bin/rm/*)
>
>	I'm not sure I understand.   I thought we retained the syntax 
>[user[:pass]@]host[:port]  for the part after the double slash even for 
>things like this.   (news is throwing me for a loop on this same point) 
>Doesn't look quite as  "Uniform"  as I had hoped.   :-( 
> 
>	Knowing that  exec:  means  "run this command"  and doesn't 
>have any relation to a protocol,  I can accept that  host, user, etc 
>information is meaningless.   In that case,  is it wrong to forbid 
>the double slash?   (enforcing a connection between double slash 
>and  host, user, etc  type information. 

  I'm wide open to suggestions on how to implement the local execution.
I just put this support in because it was something Mosaic had that I
didn't at the time, and I simply can't have that, now can I? :)

-Bill P.

home help back first fref pref prev next nref lref last post