- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Sat, 31 May 1997 23:03:46 PDT
- To: Koen Holtman <koen@win.tue.nl>
- Cc: http-wg@cuckoo.hpl.hp.com
> 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?
Regards,
Larry
--
http://www.parc.xerox.com/masinter
Received on Saturday, 31 May 1997 23:05:27 UTC