8287 2009-11-13 21:49:53 +0000 Eventing: "Implementation Considerations" - expirations and network latency 2010-03-17 11:26:24 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC All All CLOSED REMIND hasProposal P2 normal --- 1 gilbert.pilz gilbert.pilz dug lli5 public-ws-resource-access-notifications oldest_to_newest 29560 0 gilbert.pilz 2009-11-13 21:49:53 +0000 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 29616 1 lli5 2009-11-17 16:01:53 +0000 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. 30023 2 bob 2009-12-08 21:09:31 +0000 resolved as proposed