How does Receiver Endpoint assert Reliability QOS per Operation

Based on the discussions of my past emails, I would like to have this 
mail start a new thread on just a receiver
endpoint issue..

The question is:  How does a receiving endpoint assert the reliability 
qos level it supports on a per operation basis?

Example:  for the following interface definition:
Interface (Broker){

Operation Buy(in AccountNo, in StockName, in NumberOfShares):
Operation Sell(in AccountNo, in StockName, in NumberOfShares);
Operation UpdateInfo(in AccountNo, in CustomerAddress, in CustomerPhoneNo);
Operation query (in AccountNo, out SequenceOf {StockName, NumberOfShares}
}

when bound to a soap endpoint,
Buy and Sell need to be protected for guaranteed delivery, duplicate 
elim, and ordered delivery.

UpdateInfo only needs to be protected for guaranteed delivery (it is 
idempotent).

Query needs no reliability Qos.

the query operation would not use ws-reliability at all.
 

-- 
----------------------------------------------------
Tom Rutt	email: ; 
Tel: +1 732 801 5744          Fax: +1 732 774 5133