- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Jan 2011 18:12:26 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894 Summary: Eventing/Enum: duration in responses Product: WS-Resource Access Version: PR Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: dug@us.ibm.com QAContact: public-ws-resource-access-notifications@w3.org In SubscribeResponse it says that the expires time (when its a duration) is the time the subscription will expire based on when the subscription was created. However, when this expires time appears in GetStatusResponse and RenewResponse its not clear what the duration start-time is. We should clear up if its the start-time of the Subscription or of the request message. If its the start-time of the Subscription then I'm not really sure how useful this is. If the client uses GetStatus to get the expires time then there's a good possibility that they don't have the start-time of the subscription - if they did then I suspect they would know the expires time they got in the SubscribeResponse. Proposal: We should make the GrantedExpires time (when its a duration) into "how much time is left". This applies to enum too. -- 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, 27 January 2011 18:12:27 UTC