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

[Bug 7478] New: subscription expiration negotiation is incomplete and inefficient

From: <bugzilla@wiggum.w3.org>
Date: Tue, 01 Sep 2009 18:43:39 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7478-2780@http.www.w3.org/Bugs/Public/>

           Summary: subscription expiration negotiation is incomplete and
           Product: WS-Resource Access
           Version: PR
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org

The current mechanism in WS-Eventing for negotiating subscription expiration is
incomplete and inefficient. The Subscriber should be able to specify any of the
following constraints:

1. I don't care what the expiration time is - I can live with whatever the
Event Source decides.

2. I need an expiration time that is no less than X.

3. I need a Subscription that does not expire.

The Event Source should either create a Subscription within these constraints
or fault.

Currently WS-Eventing treats the Subscribers expiration constraints as
advisory. Regardless of the absence/presence or value of the wse:Expires in the
wse:Subscribe request, the Event Source is free to create a Subscription with
any expiration value it sees fit. This leaves the Subscriber with no recourse
other than to examine the /wse:SubscribeResponse/wse:Expires value (if such
exists) and Unsubscribe if it can't accept this value. This is inefficient both
in terms of coding as well as the runtime and resource costs of creating a
Subscription that is then immediately Unsubscribed-ed by the Subscriber.

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, 1 September 2009 18:43:48 UTC

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