Differences

This shows you the differences between two versions of the page.

Link to this comparison view

glosari-xmpp [2012/06/06 12:15] (current)
Line 1: Line 1:
 +====== Articles sobre XMPP ======
 +  * [[http://​oriolrius.cat/​blog/​2009/​07/​21/​glosari-de-telepathy|Glosari sobre Telepathy]]
 +
 +====== Documents interessants XMPP ======
 +
 +Per accedir als documents sobre aquesta temàtica, cal accedir al repostori: ​
 +
 +http://​91.121.177.102/​svn/​wiki-media/​xmpp/​docs/​
 +
 +
 +====== Glosari d'XMPP ======
 +
 +  * telepathy developer'​s manual: http://​people.collabora.co.uk/​~davyd/​telepathy-book/​
 +
 +  * tapioca: Tapioca is a framework for Voice over IP (VoIP) and IM applications. Its main goal is to provide an easy way for developing and using VoIP/IM services in any kind of application. It provides a pluggable interface for different protocols, such as SIP/XMPP - http://​tapioca-voip.sourceforge.net/​wiki/​index.php/​Tapioca
 +
 +  * glabbe: Gabble is a Jabber connection manager.
 +
 +  * Mission Control - Mission Control is responsible for the management of messaging accounts, the creation of connections (if an account is considered online) and setting the user's requested presence for that account. - http://​mission-control.sourceforge.net/​
 +
 +  * farsight: video conferencing made easy
 +
 +  * Stream Engine: Stream Engine effectively exports Farsight to D-Bus. When it's told to handle a particular streamed media channel, it creates sessions and streams that mirror the channels'​s session handlers and stream handlers. Singals raised and methods called by the connection manager are translated to Farsight and vice versa. (http://​telepathy.freedesktop.org/​wiki/​Streamed%20Media)
 +
 +  * Tubes: ​ Tubes are Telepathy'​s mechanism for supporting arbitrary data transfer and remote IPC. (http://​telepathy.freedesktop.org/​wiki/​Tubes) - The idea behind tubes is: "If I can talk with this person over some IM protocol, why can't program on my machine talk to programs on their machine?"​ There'​s lots of programs you have that you might want to be able to talk to their programs. E.g. your VNC client, their VNC server. For OLPC, those programs are activities.
 +
 +  * Stream tubes are useful for applications that already uses TCP because the application protocol does not need to be changed to use Telepathy tubes. Applications that uses D-Bus tubes need to have a specific protocol. Applications can use several types of tubes.
 +
 +  * Stream tubes currently means TCP. UDP tubes may be added in the future. (http://​telepathy.freedesktop.org/​spec/​org.freedesktop.Telepathy.Channel.Type.StreamTube.html)
 +
 +  * When a contact A offer a stream tube in a chatroom, it's equivalent to listening on a TCP socket with listen()/​accept(). Then anyone in the chatroom who can see the stream tube can connect to that socket as a client. For 1-1 stream tubes only one person can see the tube, but the applications can still connect to contact A multiple times. So it's really a factory for 1-1 connections. If the contact A is offering httpd over a tube, the other contact'​s firefox instance can open multiple tcp connections to the httpd.
 +
 +  * IB means In Band. The tubes' data use the same path as other messages. For XMPP (Gabble) it means the tubes' data is encapsulated in XML stanza and sent to a jabber server. It could be very slow for applications like VNC.
 +
 +  * OOB means Out Of Band. The tubes' data use a different path than other messages. The tubes' data is sent directly to the remote contact. ​
 +
 +  * Empathy: telepathy client
 +
 +  * ejabberd: servidor xmpp programat amb erland - http://​www.ejabberd.im/​tutorials
 +
 +  * XEP-0095: Stream Initiation This specification defines an XMPP protocol extension for initiating a data stream between any two XMPP entities. The protocol includes the ability to include metadata about the stream and provides a pluggable framework so that various profiles of stream initiation can be defined for particular use cases (such as file transfer).
 +
 +  * XEP-0065: SOCKS5 Bytestreams Abstract:​ This document defines an XMPP protocol extension for establishing an out-of-band bytestream between any two XMPP users, mainly for the purpose of file transfer. The bytestream can be either direct (peer-to-peer) or mediated (though a special-purpose proxy server). The typical transport protocol used is TCP, although UDP may optionally be supported as well.
 +
 +  * MUC : multi-user chat
 +
 +  * XEP-0163: Personal Eventing Protocol Abstract:​ This specification defines semantics for using the XMPP publish-subscribe protocol to broadcast state change events associated with an instant messaging and presence account. This profile of pubsub therefore enables a standard XMPP user account to function as a virtual pubsub service, easing the discovery of syndicated data and event notifications associated with such an account.
 +
 +  * GeoClue: The Geoinformation Service - http://​www.freedesktop.org/​wiki/​Software/​GeoClue
 +Geoclue is a modular geoinformation service built on top of the D-Bus messaging system. The goal of the Geoclue project is to make creating location-aware applications as simple as possible. ​
 +
 +  * XEP-0080: User Location - Abstract:​ This specification defines an XMPP protocol extension for communicating information about the current geographical or physical location of an entity.
 +
 +  * JavaScript clients: http://​blog.jwchat.org/​jwchat/​features/​
 +