W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > November 2009

[Bug 8287] Eventing: "Implementation Considerations" - expirations and network latency

From: <bugzilla@wiggum.w3.org>
Date: Tue, 17 Nov 2009 16:01:54 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1NAQV8-0004Nl-Ai@wiggum.w3.org>

Li Li <lli5@avaya.com> changed:

           What    |Removed                     |Added
                 CC|                            |lli5@avaya.com

--- Comment #1 from Li Li <lli5@avaya.com>  2009-11-17 16:01:53 ---
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.

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 Tuesday, 17 November 2009 16:02:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:37 UTC