W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > July 2009

[Bug 7127] New: Can event information contained in notification be bound to soap:headers

From: <bugzilla@wiggum.w3.org>
Date: Tue, 21 Jul 2009 21:11:54 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7127-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7127

           Summary: Can event information contained in notification be bound
                    to soap:headers
           Product: WS-Resource Access
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: tom@coastin.com
         QAContact: public-ws-resource-access-notifications@w3.org


I think there is a general understanding the concept of “information content
associated with event”.

This is the “stuff” which is relevant to applications which want to receive the
application level information for an event report which is conveyed in a
notification.

For example, the delivery “stuff’ , (eg. Notify to  for the default “push”
semantics) is not part of the application data for the event.

This distinction is important when considering implementations which recieve a
ws-eventing notification, and, subsequently, distribute the application
relevant event information to downstream subscribers outside of the ws-eventing
model (e.g, using JMS).

Proposed solution:

Define a concept of  “event information” which is that part of the notification
which conveys the application specific data associated with the event.

Have the spec clarify that this event information MUST not be bound to
soap:headers.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Tuesday, 21 July 2009 21:12:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 July 2009 21:12:04 GMT