[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - New Action Item #0009 SenderKey should be required for Notification and Completed operations
OASIS Asynchronous Service Access Protocol TC member, Keith Swenson (kswenson@us.fujitsu.com) has created a new action item. Number: #0009 Description: SenderKey should be required for Notification and Completed operations Owner: Mayilraj Krishnan (mkrishna@cisco.com) Due: 31 Jul 2004 Comments: Keith Swenson 2004-07-02 22:23 GMT The SenderKey was made optional for the case that you do not have an observer. But in the case of notifications and completed events, which come the other way, the SenderKey should not be optional. In these cases it is important to know where the event came from. I will raise this as an issue > -----Original Message----- > From: karl.dauner@boxalino.de [mailto:karl.dauner@boxalino.de] > Sent: Thursday, July 01, 2004 7:13 AM > > I studied the ASAP specification in detail and now i have a > question about the Observer resource. > When a Observer resource gets a StateChanged message how can > it identify the Instance resource which sent the message? > The body of the StateChanged message doesn't contain an > InstanceKey and within the request header the SenderKey is optional. > > Kind regards > Karl Dauner > > ---- > Karl Dauner > Boxalino Deutschland GmbH > www.boxalino.de View Details: http://www.oasis-open.org/apps/org/workgroup/asap/members/action_item.php?action_item_id=630 PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]