Tubes: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
(Link to proto XEPs on Telepathy page)
Line 16: Line 16:


In terms of the Telepathy API, we have created a channel type which has methods for enumerating existing tubes and requesting new ones. The channel might be attached to an existing channel (such as a MUC), in which case it will be automatically closed when the underlying channel is closed.
In terms of the Telepathy API, we have created a channel type which has methods for enumerating existing tubes and requesting new ones. The channel might be attached to an existing channel (such as a MUC), in which case it will be automatically closed when the underlying channel is closed.

==Proposed Standards==

See [[Telepathy#Proposed Standards]] for proto XEPs.


==More on Tubes==
==More on Tubes==
Line 24: Line 28:


[http://www.robot101.net/2007/05/11/tubes-and-planets/ Rob McQueen's blog]
[http://www.robot101.net/2007/05/11/tubes-and-planets/ Rob McQueen's blog]




==See also==
==See also==
*'''[[Low-level_Activity_API#Tubes]]'''
*[[Low-level_Activity_API#Tubes]]
*[[Shared Sugar Activities]]
*[[Shared Sugar Activities]]
*[[Tubes Tutorial]]
*[[Tubes Tutorial]]

Revision as of 11:26, 6 February 2008

Data transfer via Telepathy

A tube is a Telepathy primitive for sending and receiving data, which can be to one person or to a group of people. Tubes can carry reliable byte streams or unreliable datagrams by analogy to TCP or UDP. When a tube is to a group, some different semantics may be more appropriate, since a shared stream is not coherent. It is up to the connection manager how tubes are implemented on top of its protocol.

There are two types of Tubes at present: D-Bus Tubes and Stream Tubes.

D-Bus Tubes provide D-bus functionality to signal and call methods on everyone in the room.

Stream Tubes wrap TCP/IP sockets and are more suited to streaming data between two participants.

D-Bus Tubes

A multi-user tube is represented as a D-Bus bus, and the connection manager makes a mapping between the participants in the tube and D-Bus bus name. Clients can then take advantage of D-Bus's serialisation and the bindings so that they have to do less protocol work.

Tubes Channel Type

In terms of the Telepathy API, we have created a channel type which has methods for enumerating existing tubes and requesting new ones. The channel might be attached to an existing channel (such as a MUC), in which case it will be automatically closed when the underlying channel is closed.

Proposed Standards

See Telepathy#Proposed Standards for proto XEPs.

More on Tubes

Tubes protocol (discussion)

Dafydd Harries on Tubes

Rob McQueen's blog

See also