[Standards] Client Acknowledgement of Subscription State Change Notifications

Robert McQueen robert.mcqueen at collabora.co.uk
Wed Mar 28 20:33:04 UTC 2007

Robert McQueen wrote:
> So, we also added a hack to prevent the looping which compares it to our
> idea of the roster state, so if we've either received the <presence>
> subscription notification once already (once around the loop), or we got
> the roster node pushed to us first, we don't acknowledge it. Which isn't
> quite RFC compliant because servers are can push the node to us before
                                      ^^^^^^^ are allowed to
> the notification, but it didn't look like anyone really cared enough for
> me to bother with a more elegant solution.

Not had enough coffee today, clearly. :)

More information about the Standards mailing list