This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7828 - WS-Eventing & WS-Enum GrantedExpires type may be different
Summary: WS-Eventing & WS-Enum GrantedExpires type may be different
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Li Li
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-10-07 15:05 UTC by Li Li
Modified: 2009-12-08 22:11 UTC (History)
1 user (show)

See Also:

Attachments

Description Li Li 2009-10-07 15:05:54 UTC 
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.