W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997

Re: New feature negotiation syntax

From: Larry Masinter <masinter@parc.xerox.com>
Date: Sat, 31 May 1997 23:03:46 PDT
Message-Id: <339110C2.7CE6@parc.xerox.com>
To: Koen Holtman <koen@win.tue.nl>
Cc: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3386
> Call for opinions: If you would like to see a TCN requirements
> document, please say so on the list or in private e-mail, in which
> case I'll summarize on the list.  Note that a TCN requirements
> document will contain things like `it has to be a HTTP extension' and
> `it must not rely on Java or any other scripting language'.  This
> document will not contain all requirements for all forms of
> negotiation.

Such a document would be useless. The question is not "why this
particular TCN proposal", but  "what problem is it that TCN
is supposed to solve".

I think the main requirement is:
  - Allow a single resource identified by a single URL to
    serve different entities to different clients without
    the client having to a priori send all of its features
    and capabilities with each request.

I think there may be a few other requirements, too, but
what? And if the above is the only requirement, then 
why _not_ dynamic content?


Received on Saturday, 31 May 1997 23:05:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:20 UTC