- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 07 Oct 2009 15:05:54 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828 Summary: WS-Eventing & WS-Enum GrantedExpires type may be different Product: WS-Resource Access Version: FPWD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: lli5@avaya.com QAContact: public-ws-resource-access-notifications@w3.org WS-Eventing Section 4.1: [Body]/wse:SubscribeResponse/wse:GrantedExpires The expiration time assigned by the event source. The expiration time MAY be either an absolute time or a duration but SHOULD be of the same type as the requested expiration (if any). WS-Enumeration Section 3.1: [Body]/wsen:EnumerateResponse/wsen:GrantedExpires The expiration time assigned by the data source. The expiration time MAY be either an absolute time or a duration but SHOULD be of the same type as the requested expiration (if any). In both cases, the specs allow the server to return an expiration time that has different type as requested by the client. For example, the server returns an absolute time for a requested duration. This can create problems for clients that only support the requested expiration type. Proposal: change "SHOULD" in the above statements to "MUST" in both specs. -- 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, 7 October 2009 15:05:58 UTC