[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Issue 094 - DPWS - Clarification on time-type for SubscriptionDuration
Following the discussion on the conference call on Tuesday, I
put together some text that explains R3005 and R3006. This is a set of changes
to the paragraph that follows R3013. Updated text in red. Event Sources are required to have
an internal clock, but there is no requirement that the clock be synchronized with
clients or other HOSTED SERVICEs. Event Sources are only required to support Expirations
expressed in duration, but they should attempt to match the type of the
Subscription Expiration when possible. If the value or type of the
Expiration is unacceptable, the Event Source may select an appropriate
Expiration and return it in the Subscribe Response or Renew Response. Adding this text should explain how devices may handle expiration
types/values, and should allow us to remove R3005 and R3006. --D From: Ram Jeyaraman
[mailto:Ram.Jeyaraman@microsoft.com] This issue is assigned
the number 094. For further discussions on this issue, please refer to this
issue number or use this thread. From: Scott de Deugd
[mailto:dedeugd@us.ibm.com]
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]