Alex Rousskov wrote:
You are right that this is pretty much unrelated to the callout
protocol: calls should no go out if OPES is being bypassed. The only
related aspect is that the callout protocol may have to pass user
bypass instructions/preferences _if_ we want to support selective
bypass (e.g., "bypass only this OPES/service"). I am not sure we need
that kind of selectivity at this point.
Isn't this kind of selectivity provided by the OPES rules? If a user
wants to use OPES services, in general, but wants to bypass specific
services, this should be reflected in the user's rules rather than
"in-band" in application messages...
With respect to the callout protocol possibly having to pass user
bypass instructions/preferences... I assume the OPES processor
includes explicite instructions on which services to execute in the
callout protocol messages. As such, not including a specific service
implies that it won't be executed, implicitely implementing a "bypass".
Think we're in agreement...
The first thing to decide is probably OPES identification/addressing
system that will be shared by both tracing and bypass OPES features.
What do we want to identify and/or address?
- just OPES processors
- OPES processors and callout servers
- OPES processors, callout servers, and services
- other?
For tracing it seems we need to identify all three, meaning OPES
processors, callout servers, and the services, implying we need an
identification/adressing cheme for all three of them. This should also
cover the bypass and debugging feature.
-Markus