[Telepathy] The XMPP implementation of Tubes

Guillaume Desmottes guillaume.desmottes at collabora.co.uk
Thu Aug 16 02:22:13 PDT 2007

Le lundi 13 août 2007 à 18:20 +0100, Simon McVittie a écrit :
> On Mon, 13 Aug 2007 at 17:49:46 +0100, Simon McVittie wrote:
> > To offer a tube, send a Stream Initiation request with profile
> > NS_SI_TUBES or NS_SI_TUBES_OLD (currently, the latter is sent).
> Clearly wrong, we should use the correct namespace.

> > It's somewhat vague whether we support opening a 1-1 tubes channel with
> > a MUC contact - there is code to support it, but I don't think we put
> > capabilities in MUC presence. We should probably rule that it's
> > unsupported.
> What I said.

> > In the case of D-Bus tubes, each <message> contains (a) an entire
> > D-Bus message, and (b) no more than one D-Bus message.
> In 1-1 tubes we should support arbitrary fragmentation - it's relatively
> simple to parse enough of a D-Bus message to be able to find message
> boundaries.
> > The messages are sent in <message>s as specified by IBB (XEP-0047_), except
> > that the sequence number @seq is meaningless on output, must be ignored
> > on input, and no <open> or <close> ever occurs.
> I propose sending <message><data xmlns=NS_TUBES>base64</data></message>.
> The data element should also have an optional attribute "frag" or
> something, with values "first", "middle", "last"; omitting the attribute
> means it's a complete message (i.e. simultaneously first and last).

That means we should implement a new type of bytestream.
TubeBase64Bytestream or something.


More information about the Telepathy mailing list