[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Separation of Sender and Receiver Qos Assertions
Doug wrote Tom and Chris, Am I correct that we are discussing two separate issues here? On one hand, we have the already-logged issue about senders asserting requirements for reliability assurance on the receiver. On the other, we have the question Tom originally raised in this thread about the granularity of a receiver's declarations. If I am correct, could we at least split these issues into separate threads? thanx, doug I now see that there are two separate issues. 1) how does a receiver application endpoint assert reliabiity qos level it supports on a per operation basis. I believe the interface below is a sufficient use case to justify this first issue: >>>>>> 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} >>>> >>>> >>>>>> } 2) is there a requirement to allow the sender to assert reiliability qos levels on a per sequence basis? The use case for this second issue is what I think Chris F is calling into question. Tom Rutt -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]