Introduction
Rudel has several kinds of backends: protocol backends, transport backends and session initiation backends. This page lists Rudel backends grouped by these categories, explains their purpose and states their respective status.
Protocol Backends
| Name | Synopsis | Status | Quality |
|---|---|---|---|
| Obby | The obby protocol backend implements the client and server part of the obby protocol. It enables Rudel clients to join sessions hosted by Gobby servers or Rudel servers. However, it is currently not possible for Gobby clients to join sessions which are hosted by Rudel servers. | complete | robust |
| Infinote | The infinote protocol backend implements the client part of the infinote protocol. It enables Rudel client to join sessions hosted by Gobby servers or Rudel servers. However, it is currently not possible for Gobby clients to join sessions which are hosted by Rudel servers. | incomplete | unstable |
| SubEthaEdit | started | ||
| Wave | planned | ||
| EtherPad | started |
Transport Backends
| Name | Synopsis | Status | Quality |
|---|---|---|---|
| Socket/TCP | This backend is just a thin wrapper around Emacs' socket API. | complete | robust |
| XMPP | This backends transports Rudel payload over XMPP streams. The infinote protocol backend requires this transport backend when talking to an infinoted server and Gobby clients. Rudel, however, can use this backend to transport arbitrary payloads. | almost complete | pretty robust |
| BEEP | BEEP is a meta-protocol (or framework) which can be used to construct application protocols. Its primary application in Rudel is transporting payloads for the SubEtha protocol. | incomplete | |
| IRC | The IRC transport backend uses ERC to exchange payloads over the IRC network. A principle problem of this backend is the limited bandwidth due to the flood-protection of IRC servers. | almost complete | unstable |
| Telepathy | This backend uses the Telepathy software stack to transport payloads between contacts participating in chat sessions. In principle, any protocol supported by Telepathy can be used. | started |
Session Initiation Backends
| Name | Synopsis | Status | Quality |
|---|---|---|---|
| Zeroconf | This backend collaborates with the Avahi daemon to advertise and discover Rudel and Gobby sessions on the local network. Joining advertised sessions is convenient because it does not require entering connection information such as server name, port and encryption. | almost complete | robust |
| IRC | This backend advertises and discovers Rudel sessions in IRC channels. It aims at providing ad-hoc collaborative editing via IRC with minimal configuration effort. | almost complete | unstable |
