--On Thursday, November 22, 2001 13:39 +0100 Volker Hilt
<hilt(_at_)informatik(_dot_)uni-mannheim(_dot_)de> wrote:
> " To invoke multiple services, an intermediary MUST be able to
> specify more than one URL. "
>
> Here you are implying that URL as a means for Service Identification
> MUST always be supported. This should be MAY or better just rewrite it
> so that whatever method used (embbebed URL or a new header, or even
> different combination of channels) asking for several services on the
> same content MUST be possible.
Doing it in a header? I'd hate to think of the consequences if
someone's HTTP server just happened to start injecting headers that
caused unexpected activity in OPES systems...
Hmmm, the header is part of the callout protocol (not of the conent path
message). So a web server is never able to generate these headers.
One would hope so.
But in that case, if the header is attached to the callout protocol, then
surely it must have been possible to address the service in some way (hmm,
maybe like a URI perhaps).