On Feb 25, 2009, at 7:36 PM, Pavel Simerda wrote:
On Tue, 24 Feb 2009 15:54:38 +0000
Pedro Melo <[email protected]> wrote:
Hi,
On Feb 24, 2009, at 12:49 AM, Pavel Simerda wrote:
There are several cases when subscription databases in XMPP are
inconsistent.
You may view subscription information as a global distributed
database.
Subscription state between two JIDs, for example a...@a and b...@b are
stored
in two places at the same time. Servers A and B maintain their own
copies of subscription state.
[....]
What with the roster items that are inconsistent?
* Mark as inconsistent, let the client present it to the user to
take action.
* Auto-repair and thus maintain consistency
Looking forward to all feedback.
When you send out a <presence type="probe" /> include the local
"view" of the subscription state.
Btw presence probe seems too weak... as it doesn't reveal full
subscription state.
that's what I'm saying: include the full subscription state in the
presence probe so that the other side can detect mis-matches.
Best regards,
