< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index

RE: [reSIProcate] Change to ClientSubscription

From: "Derek MacDonald" <derek@xxxxxxxxxxxxxxx>
Date: Thu, 22 Dec 2005 18:04:44 -0800

This was committed in rev 5767.

--Derek

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Derek MacDonald
Sent: Thursday, December 22, 2005 11:28 AM
To: 'Resip Devel'
Subject: [reSIProcate] Change to ClientSubscription

ClientSubscription is being changed to deal with overlapping NOTIFY transactions. The app will receive the NOTIFY callbacks in a serialized fashion. An onUpdateFoo callback will not happen until that notify has been accepted or rejected.

There is one minor api change: the onUpdateFoo callbacks provide an additional boolean parameters, which indicates whether that NOTIFY message has been received out of order.

This will most likely be committed later today.

--Derek

References:
- [reSIProcate] Change to ClientSubscription
  - From: Derek MacDonald

Prev by Date: [reSIProcate] Change to ClientSubscription
Next by Date: [reSIProcate] Doubt regarding how the Presence information of clients is achieved in SIP
Previous by thread: [reSIProcate] Change to ClientSubscription
Next by thread: [reSIProcate] Doubt regarding how the Presence information of clients is achieved in SIP
Index(es):
- Date
- Thread