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

[Bug 9702] Eventing: Add a wse:ExpirationTimeConstraintsNotSupported fault

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 May 2010 01:10:13 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OCMwH-0001Gk-Td@jessica.w3.org>

Ram Jeyaraman <ram.jeyaraman@microsoft.com> changed:

           What    |Removed                     |Added
                 CC|                            |ram.jeyaraman@microsoft.com

--- Comment #4 from Ram Jeyaraman <ram.jeyaraman@microsoft.com>  2010-05-13 01:10:13 ---
Consequent to what we discussed today about simplifying the existing semantics
for specifying a subscription expiry time, I like to propose the following
refinement to what was discussed today [1]:

1) Expires is server optional, add a fault to indicate non-support, and add an
ExpiresSupported policy assertion parameter.

2) If Expires is absent, server chooses an appropriate duration for

3) If Expires is present:

If attribute ‘exact’ is present, the server must honor the requested duration
or reject the subscription with a fault.

If the attribute ‘exact’ is absent (default behavior) , the requested duration
is a hint. This allows the event source to better accommodate the client
preferences when it grants a time duration for subscription.

[1] Direction discussion today

“Expires is server optional, add a fault for when its not, add a
ExpiresSupported policy assertion, Subscribe w/o Expires == server chooses,
Subscribe + Expires == match the time/duration or fault”

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 Thursday, 13 May 2010 01:10:15 UTC

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