Difference between revisions of "Tech pages/Multi-User Chat"

From XMPP WIKI
Jump to navigation Jump to search
(wiki formatting)
Line 1: Line 1:
XMPP Technologies: MUC
+
== Overview ==
Table of Contents
 
 
 
1. Overview
 
2. Specifications
 
3. Implementations
 
    1. Servers
 
    2. Server Components
 
    3. Clients
 
    4. Libraries
 
4. Discussion Venues
 
 
 
1. Overview
 
  
 
MUC is Multi-User Chat, an XMPP extension for multi-party information exchange similar to Internet Relay Chat (IRC), whereby multiple XMPP users can exchange messages in the context of a room or channel. In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. Because MUC rooms are based on XMPP, they can be used to exchange not only plaintext message bodies but a wide variety of XML payloads.
 
MUC is Multi-User Chat, an XMPP extension for multi-party information exchange similar to Internet Relay Chat (IRC), whereby multiple XMPP users can exchange messages in the context of a room or channel. In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. Because MUC rooms are based on XMPP, they can be used to exchange not only plaintext message bodies but a wide variety of XML payloads.
  
2. Specifications
+
== Specifications ==
  
 
MUC is defined in one primary specification (XEP-0045) and several ancillary specifications:
 
MUC is defined in one primary specification (XEP-0045) and several ancillary specifications:
 
 
* XEP-0045: Multi-User Chat
 
* XEP-0045: Multi-User Chat
 
* XEP-0249: Direct MUC Invitations
 
* XEP-0249: Direct MUC Invitations
 
* XEP-0272: Multiparty Jingle
 
* XEP-0272: Multiparty Jingle
  
3. Implementations
+
== Implementations ==
3.1 Servers
+
 
 +
=== Servers ===
  
 
The following XMPP servers include built-in support for MUC:
 
The following XMPP servers include built-in support for MUC:
 
 
* ejabberd
 
* ejabberd
 
* Jabber XCP
 
* Jabber XCP
Line 34: Line 21:
 
* Tigase
 
* Tigase
  
3.2 External Components
+
=== External Components ===
  
 
The following standalone components can be used with a wide variety of XMPP servers:
 
The following standalone components can be used with a wide variety of XMPP servers:
 
 
* mu-conference
 
* mu-conference
 
* palaver
 
* palaver
  
3.3 Clients
+
=== Clients ===
  
 
* Adium
 
* Adium
Line 50: Line 36:
 
* Psi
 
* Psi
  
3.4 Libraries
+
=== Libraries ===
  
 
* AnyEvent:XMPP (Perl)
 
* AnyEvent:XMPP (Perl)
Line 59: Line 45:
 
* XMPP4R (Ruby)
 
* XMPP4R (Ruby)
  
4. Discussion Venues
+
== Discussion Venues ==
  
 
The XMPP Standards Foundation maintains a dedicated email list ("muc@xmpp.org") about MUC, intended as a low-volume venue for discussion of MUC implementation and protocol issues. As with all XSF technology lists, the muc@xmpp.org list is open to all interested individuals.
 
The XMPP Standards Foundation maintains a dedicated email list ("muc@xmpp.org") about MUC, intended as a low-volume venue for discussion of MUC implementation and protocol issues. As with all XSF technology lists, the muc@xmpp.org list is open to all interested individuals.

Revision as of 22:57, 17 February 2010

Overview

MUC is Multi-User Chat, an XMPP extension for multi-party information exchange similar to Internet Relay Chat (IRC), whereby multiple XMPP users can exchange messages in the context of a room or channel. In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. Because MUC rooms are based on XMPP, they can be used to exchange not only plaintext message bodies but a wide variety of XML payloads.

Specifications

MUC is defined in one primary specification (XEP-0045) and several ancillary specifications:

  • XEP-0045: Multi-User Chat
  • XEP-0249: Direct MUC Invitations
  • XEP-0272: Multiparty Jingle

Implementations

Servers

The following XMPP servers include built-in support for MUC:

  • ejabberd
  • Jabber XCP
  • Openfire
  • Prosody
  • Tigase

External Components

The following standalone components can be used with a wide variety of XMPP servers:

  • mu-conference
  • palaver

Clients

  • Adium
  • Gajim
  • JWChat
  • mcabber
  • Pidgin
  • Psi

Libraries

  • AnyEvent:XMPP (Perl)
  • gloox (C++)
  • jabber-net (.Net)
  • libpurple (C)
  • Smack (Java)
  • XMPP4R (Ruby)

Discussion Venues

The XMPP Standards Foundation maintains a dedicated email list ("muc@xmpp.org") about MUC, intended as a low-volume venue for discussion of MUC implementation and protocol issues. As with all XSF technology lists, the muc@xmpp.org list is open to all interested individuals.

  • Info page and subscription information
  • Subscribe via email
  • Discussion archives