Re: proposal for new HTTP/1.0 directive

• Mail folder: WWW Talk Oct 93-present
• Next message: Rob McCool: "Re: cc:Mail SMTPLINK 2.0 Undeliverable Message"
• Previous message: Mr Robert McArthur: "Re: Mosaic USENET client?"
• In-reply-to: Marc Andreessen: "proposal for new HTTP/1.0 directive"
• Reply: Marc Andreessen: "Re: proposal for new HTTP/1.0 directive"

Message-id: <9311300157.AA07983@void.ncsa.uiuc.edu>
From: robm@ncsa.uiuc.edu (Rob McCool)
Date: Mon, 29 Nov 1993 19:57:34 -0600
In-Reply-To: marca@ncsa.uiuc.edu (Marc Andreessen)
       "proposal for new HTTP/1.0 directive" (Nov 27,  2:28pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: marca@ncsa.uiuc.edu (Marc Andreessen), www-talk@nxoc01.cern.ch
Subject: Re: proposal for new HTTP/1.0 directive

/*
 * proposal for new HTTP/1.0 directive  by Marc Andreessen (marca@ncsa.uiuc.edu)
 *    written on Nov 27,  2:28pm.
 *
 * It occasionally is useful to have the results of a HTTP/1.0
 * transaction return *nothing* (no significant response data) -- the
 * client should not display a new document or do anything else other
 * than stay on exactly the same document it's already on.
 * 
 * An example of where this would be useful: tape-deck-style
 * fast-forward/stop/reverse/play/pause/etc. controls implemented with
 * forms or hyperlinks as part of a multicasting transmission
 * application.  You want to be able to trigger as many actions as you
 * want (play, pause, play, fast-forward, play, etc.) without moving to a
 * different document each time.
 * 
 * How about "204 NoResponse"?
 */

I second the motion. I've gotten several people asking for a way to do that
exact thing from scripts.

--Rob