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
cop
Feedback mostly discussed in the jdev conference:
* bidirectional s2s could be announced in sent
right after the opening tag from the initiator.
* connection reuse for multiple s2s links would be a very useful
feature, ask Dave for details
* resource conflicts should be handled consistentl
Peter Saint-Andre wrote:
> As promised at the XMPP Summit, I've been working on some revisions to
> XEP-0047 (In-Band Bytestreams). The changes consist of clarifying packet
> processing and error handling, adding more examples, recommending IQs
> over messages, correcting the schemas, etc. You can
Alexander Gnauck wrote:
> Peter Saint-Andre schrieb:
>> Feedback is welcome, especially from Justin. :)
>
> I will use IBB in a project for sending big data objects. So not files
> directly. Because it well designed for splitting any data in chunks.
>
> So we could add other examples and use case
At its next meeting (Wednesday), the XMPP Council will have a chat about
the XMPP BOF @ the IETF. Read on for more information. As always, anyone
can join the Council meeting.
Original Message
Subject: Re: [Council] XMPP BOF @ IETF 74
Date: Mon, 23 Feb 2009 15:58:34 -0700
From: P
Example 208 shows the as child of
cauldronburn
Example 124 has the as child of
cauldronburn
which one is correct. I think the second one.
is missing in the schema of
Also if 208 is correct ;-)
Peter Saint-Andre schrieb:
Feedback is welcome, especially from Justin. :)
I will use IBB in a project for sending big data objects. So not files
directly. Because it well designed for splitting any data in chunks.
So we could add other examples and use cases than only file transfer to it.