On Wed, 12 Mar 2003, Markus Hofmann wrote:
But for a general OPES bypass, I don't see that interaction between
the application protocol and the OPES callout protocol would be
required. If the user signals "no OPES, please", the callout
protocol is not involved at all.
Please see my opes:filtering/cisco-defaults example with processing
delegation and related changes of the service ID. I am not sure if
that is legal OPES, but it does seem to require callout server
involvement.
Hm... I tend to believe the callout servers must participate in
tracing, since the user doesn't really know on which specific server
a requested service will be executed (i.e. we assume late service
binding for now). If the user now suspects that something goes
wrong, (s)he better want to know what specific servers have been
involved. Hm, however, this information is probably readily
available on the OPES processor and the OPES processor might insert
the approriate tracing info... Would that be enough?
I think the answer depends on how "late" your binding is: can a
callout server delegate processing to another callout server? If yes,
the original OPES dispatcher/processor does not have enough
information and the callout server should pass that along to the next
OPES "hop".
Alex.