Tigase Server

warning: Creating default object from empty value in /home/webapp/drupal-6.28/sites/all/modules/i18n/i18ntaxonomy/i18ntaxonomy.pages.inc on line 34.
Article is about Tigase Server

External Roster Management Strategy

Submitted by Anonymous on Wed, 2013-01-30 10:44
::

Hi,
I am planning to move out the roaster management as external component from Tigase. I am planning to route the calls for add/update roaster to external service to persist roster in another schema other than the schema Tigase is using.Calls from Tigase to get the roster will be routed to same service to get the roaster details from same schema. Schema can be updated externally from other tools to import/remove/update contacts for a user.

Does MUC send all history before live messages to the user?

Submitted by Anonymous on Tue, 2013-01-29 17:13
::

According to XEP-0045 :

The service MUST send all discussion history messages before delivering the room subject and any "live" messages sent after the user enters the room.

But from what i see on the PresenceModule code :

room.addOccupantByJid(senderJID, nickname, newRole);
...
...
...
sendHistoryToUser(room, senderJID, maxchars, maxstanzas, seconds, since, writer);

What happens if a Live message is received from another muc user after the call to room.addOccupantByJid but before the sendHistoryToUser terminates?

Tigase server cannot find custom plugin implementation

Submitted by Anonymous on Thu, 2013-01-24 21:18
::

Hi, I have developed a custom basic plugin as an example for testing, the code is very simple: ExamplePlugin.java

SASL custom mechanisms and configuration

Submitted by bmalkow on Wed, 2013-01-23 04:54
::

This API is available from Tigase XMPP Server version 5.2.0 or our current master branch.

Note that API is under active development. This description may be updated at any time.

Basic SASL configuration

SASL implementation in the Tigase XMPP Server is compatible with Java API.The same exact interfaces are used.

The SASL implementation consists of following parts:

  1. mechanism
  2. CallbackHandler

Properties list for SASL plugin (sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl):



Property Description
factory A factory class for SASL mechanisms. Detailed description at Mechanisms configuration
callbackhandler A default callback handler class. Detailed description at CallbackHandler configuration
callbackhandler-${MECHANISM} A callback handler class for a particular mechanism. Detailed description at CallbackHandler configuration
mechanism-selector A class for filtering SASL mechanisms available in a stream. Detailed description at Selecting mechanisms