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

[Bug 7970] New: Eventing: clarify role of event source

From: <bugzilla@wiggum.w3.org>
Date: Mon, 19 Oct 2009 15:07:46 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7970-2780@http.www.w3.org/Bugs/Public/>

           Summary: Eventing: clarify role of event source
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org

(from a note conversation with Antoine Mensch)
Eventing currently defines an Event Source as:
    A Web service that sends notifications and accepts requests
    to create subscriptions. 

This isn't quite accurate. An Event Source does accept requests to
create subscriptions, but who actually sends out the notifications
is an implementation detail.  For example, the endpoint that accepts
the Subscribe() could be very different from the endpoints/components
that actually send out the notifications - it could just be acting as
a sort of proxy/manager.

Modify the defn to read:

    A Web service that accepts requests to create subscriptions.

If we don't want to lose the tie-in with notifications, perhaps something
like this:

   A Web service that accepts requests to create subscriptions for
   a certain set of notification that might be generated.

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 Monday, 19 October 2009 15:07:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:36 UTC