Status Information - summary?

wmperry@indiana.edu (William M. Perry)

Mail folder: WWW Talk Apr 94-present
Next message: Murray-Rust Dr P: "ANNOUNCE MAPMARKER V0.2 - Clickable map editor"
Previous message: joe@MIT.EDU: "Announcing tkWWW-0.11"
Maybe in reply to: George Phillips: "Status Information - summary?"
Reply: George Phillips: "Status Information - summary?"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 26 Apr 1994 09:31:55 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <m0pvgcp-00000iC@monolith>
Errors-To: listmaster@www0.cern.ch
Reply-To: wmperry@indiana.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: wmperry@indiana.edu (William M. Perry)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Status Information - summary?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

>>>>> "gp" == George Phillips <phillips@cs.ubc.ca> writes:

gp> Mark Cox asks about the Status: headers:
>> Was a decision ever reached about how feasible this is?  Did anyone
>> attempt to add this?

gp> Well, it's extremely feasible.  A nph- CGI script can trivially
gp> output the Status: headers.  A quite small modification to libwww2
gp> could pass Status: contents on to the browser (look in HTMIME.c).

gp> As far as I know, noone has added it to any browser or server.  Too
gp> helpful to the user in some cases and too simple to implement, I
gp> guess.

   Send in patches and I'm sure most of us would consider merging them into
our browsers.  Otherwise, I'd say it was pretty low on the priority list
for most people.  MacMosaic wants forms, WinMosaic needs stability.  tkWWW
needs a few more things first, and all the browsers need more HTML+
capabilities.

-Bill P.