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: Wed, 12 May 2010 16:03:06 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OCEOo-0004mM-59@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702





--- Comment #2 from Antoine Mensch <antoine.mensch@odonata.fr>  2010-05-12 16:03:05 ---
wse:UnsupportedExpirationType addresses the case where a xsd:dateTime is used
as expiration spec, when only xsd:duration is supported by the event source, so
it is not related to my issue.
wse:InvalidExpirationTime means that the expiration spec is either malformed
(i.e. not a xsd:dateTime or xsd:duration), or that it does not fulfill the
constraints expressed by the @min and @max attributes (which by the way means
that the event source understands those atributes).
wse:ExpirationTimeConstraintsNotSupported would be used to reject a
subscription request using constraints when the event source is not able or not
prepared to use them. As explained in the issue description, supporting those
constraints might be a problem for small devices.  
I know that some people might claim that using faults is not the best way to
discover if optional features are supported, but note that this is exactly what
happens when wse:UnsupportedExpirationType is returned (this remark is not a
request to remove this particular 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 Wednesday, 12 May 2010 16:03:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 May 2010 16:03:07 GMT