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

[Bug 6696] Eventing: When to check the EPRs

From: <bugzilla@wiggum.w3.org>
Date: Wed, 13 May 2009 07:55:43 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1M49JX-0002Si-9X@wiggum.w3.org>

Robert Freund <bob@freunds.com> changed:

           What    |Removed                     |Added
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Robert Freund <bob@freunds.com>  2009-05-13 07:55:42 ---
Add the following to the WS-Eventing spec at the end of the Subscribe request

- - - - - - - - -
If included within the Subscribe request message, the wse:NotifyTo 
and wse:EndTo SHOULD have some cursory validity checking performed before 
the Subscribe response is returned. While not all errors can be detected
prior to sending a message to those EPRs, some obvious ones can be detected.
For example, an unsupported transport specified within the wsa:Address IRI.
Detecting these errors during Subscribe processing will lessen the chances
of the subscriber creating an unusable subscription.  If this check is
performed and a problem is detected then the event source MAY generate
a wse:UnusableEPR fault rather than returning the SubscribeResponse message.
- - - - - - - - -

and then define a wse:UnusableEPR fault - make the details element
say which EPR(s) was bad and why.  We can't use the wsa:InvalidEPR fault 
because that appears to only be for headers - no idea why  ;-)

If we accept this proposal then we should apply the same type of
change to WS-Enumeration (wsen:EndTo) as well - for consistency.

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.
Received on Wednesday, 13 May 2009 07:55:52 UTC

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