Re: behavior of ">" and ">>" in line mode browser

jfg@bernd.cern.ch (Jean-Francois Groff)
Date: Mon, 23 Mar 92 17:47:01 -2300
From: jfg@bernd.cern.ch (Jean-Francois Groff)
Message-id: <9203241647.AA15238@bernd.cern.ch>
To: www-talk@nxoc01.cern.ch
Subject: Re: behavior of ">" and ">>" in line mode browser
References: <m0lSK12-000HpjC@heifetz.msen.com>
  Thank you Ed for more useful bug reports. Here are your answers...

----------------------------------------------------------------------------
problem yacc'ing violaWWW

I don't know. I never compiled it myself... The error is not in gram.y...
Looks like your cc doesn't understand the "#if" preprocessor directive (ANSI).
Try gcc instead.

----------------------------------------------------------------------------
behavior of ">" and ">>" in line mode browser

Here's a diff on HTBrowse.c to handle this. The line numbers and the
"the_choice" variable will not correspond to your code because they're
from the unreleased 1.2e (soon to become 1.3 on ftp...)

*** 1080,1087 ****
  
                command  = (char *) malloc(
                        strlen(address)+strlen(the_choice)+30);
!               sprintf(command, 
!                       "www -n -na -p \"%s\" %s", address, the_choice);
                result = system(command);
                if (result) printf("  %s  returns %d\n", command, result);
                free(command);
--- 1080,1087 ----
  
                command  = (char *) malloc(
                        strlen(address)+strlen(the_choice)+30);
!               sprintf(command, "www -n %s \"%s\" %s", 
!                       HTDiag ? "-source" : "-na -p", address, the_choice);
                result = system(command);
                if (result) printf("  %s  returns %d\n", command, result);
                free(command);

----------------------------------------------------------------------------
rfc: "gateway"

I see your point. However, the only intention of the WWW_foo_GATEWAY syntax
is to enable access to protocols not understood by the www client by means
of a gateway that translates those to/from HTTP/HTML. Ideally, what we need
to be able to fetch RFCs properly is a naming service, x500 or whatever.
Your rfc: access is rather an address alias. For that, you could direct it
to your own HTTP server with WWW_rfc_GATEWAY, and then insert

	map	rfc:	file://ftp.nisc.sri.com/rfc/

in your httpd.conf rule file. But beware that if you start serving HTML
files with rfc: addresses instead of file://host/rfc, every www client in
the world will have to set WWW_rfc_GATEWAY.

----------------------------------------------------------------------------
WAISGate support for WAIS 'HTML' doc type

Tim answered this one. As he said, "Great!".

----------------------------------------------------------------------------
  Jean-Francois Groff (jfg@info.cern.ch)
  World-Wide Web initiative
  CERN, ECP division, CH-1211 Geneva 23, Switzerland
  Phone +41 22 767 3755 -- Fax +41 22 767 7155
--
"If we were directed from Washington when to sow and when to reap,
 we would soon want bread."
	- Thomas Jefferson