On Sun, 23 Feb 2003, jfcm wrote:
How do we zap and abort the transactions?
I assume you are talking about the situation where user request must
stop at the OPES processor or the callout server due to
rules/policies/etc.
The predraft document describes how a callout server can abort an
application transaction. The technique is based on changing the source
and destination addresses: the source address becomes the address of
the callout server. The destination address becomes the address of the
application client (it has to even point to the same application
connection if application protocol requires that). When OPES processor
receives a <message-start> OPES message with such addresses, it would
start responding to the original client request instead of forwarding
the request to the server.
As you know, Hilarie Orman (and probably others), objected to giving
callout servers ability to change source and destination addresses.
This objection would need to be resolved by either convincing
opponents that there are no good reasons to prohibit such a change OR
adding new OCP mechanisms to allow callout servers to tell OPES
processor:
"you expected me to modify the request to be forwarded, but I
am telling you to abort forwarding and respond with the
following message instead"
Note that in the current proposal, the semantics is somewhat different
(abort is not an exceptional condition in the predraft):
"you expected me to modify the application message; here is
a modified version; forward it [back to the client]"
Does the above answer your question?
Thank you,
Alex.