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 8287 - Eventing: "Implementation Considerations" - expirations and network latency
Summary: Eventing: "Implementation Considerations" - expirations and network latency
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-11-13 21:49 UTC by Gilbert Pilz
Modified: 2010-03-17 11:26 UTC (History)
2 users (show)

See Also:


Description Gilbert Pilz 2009-11-13 21:49:53 UTC
Section 8 "Implementation Considerations" starts with the following sentence:

"Implementations SHOULD generate expirations in subscribe and renew request and response messages that are significantly larger than expected network latency."

This seems like pointless advice.

Proposal: remove sentence
Comment 1 Li Li 2009-11-17 16:01:53 UTC
i guess maybe in the original spec the clock starts on the sender side, so the subscriber has to count the network delay. Now that the spec says the clock starts on the receiver's side, so the network delay, however long, is removed.

But still the subscription manager should NOT create a subscription that will expire before the subscriber gets the response, due to network delay. Otherwise, the subscriber may get a positive SubscribeResponse while the subscription has actuall expired.

However, in practice, the expiration time is probably sufficiently large already and the above scenario is unlikely to occur.
Comment 2 Robert Freund 2009-12-08 21:09:31 UTC
resolved as proposed