Programming Jabber

Custom Configuration

Configuration of the Conferencing component is straightforward and is identified with the jabber:config:conference namespace:

<conference xmlns="jabber:config:conference">
  ...
</conference>

We can see from the contents of the custom configuration that there are a number of elements:

Public or private service

Specifying (with the <public/> tag) that a conference service is public means that users are allowed to browse the elements that the service is controlling, namely, the rooms. Rooms are either precreated or created on the fly by the first user to specify a new name when requesting to join a room. Specifying (with the <private/> tag) that a conference service is private means that users are allowed to browse only rooms that they already know about, meaning rooms in which they’re already present.

vCard

The conference service component can have its own vCard information, which can be requested at any time. Here is where that vCard information can be maintained. Like the vCard for the JSM service, this particular definition uses only a few of the many possible vCard fields, for example:

<vCard>
  <FN>yak Chatrooms</FN>
  <DESC>This service is for public chatrooms.</DESC>
  <URL>http://yak/chat</URL>
</vCard>

Message history

When you join a room, it is sometimes useful to see some of the most recent messages from the room’s conversation(s). The <history/> tag allows you to specify how many previous messages are relayed to new room joiners.

If you don’t specify ...