I was talking about placing a requirement on the OPES server
implmentation, not the callout protocol itself. I.e., the protocol can
be agnostic, but the thing that stuffs HTTP messages into it had better
understand the semantics of HTTP.
On Tuesday, April 16, 2002, at 07:43 AM, Markus Hofmann wrote:
Mark Nottingham wrote:
These mechanisms are required in order to be HTTP-compliant;
therefore, I'd say they should be part of the ICAP server's HTTP stack.
Hm, this assumes that the payload (i.e. the content-path protocol) is
NOT transparent to the OPES/Callout protocol, i.e. the OPES/Callout
protocol needs to have knowledge about the sematics of the encapsulated
application protocol (HTTP in this case).
Do we want to make this assumption? Comments?
-Markus
--
Mark Nottingham
http://www.mnot.net/