PEP in MUC: An Openfire Plugin

Overview

Openfire plugin allowing users local to the server to explicitly broadcast their Personal Eventing information to a Multi-User Chat room via a command sent to the MUC room.

For example, if local user VinniePaz is in a MUC room and wishes to share what he is listening to with the other occupants in the room, he can send a message to the room with body "/tune" which will cause the server to lookup his User Tune PEP node and share its payload with the other room occupants in an action format.

(eg. VinniePaz is listening to Jedi Mind Tricks - Blood Runs Cold - Violent By Design)

The plugin aims to support all known PEP data formats, triggered by their node names in the form of a command. So if the user wishes to broadcast his 'mood' PEP node, he could send a message to the room with body "/mood".

Requirements

You need to be using a version of Openfire greater than 3.5.1 (so currently, from svn trunk).

However, if you do not want to build from trunk and you cannot wait for the next Openfire release, you can download a patched openfire.jar lib file for version 3.5.1 and copy it over your old openfire.jar in the openfire/lib/ directory.

Installation

Copy pepInMuc.jar into the plugins directory of your Openfire installation. The plugin will then be automatically deployed. To upgrade to a new version, copy the new pepInMuc.jar file over the existing file.

Using the Plugin

As a local user, join a MUC room. Send a message to the room with body "/<PEP_Node_Name>" where <PEP_Node_Name> is the name of a PEP node the plugin supports.

Currently, the plugin supports the following PEP node types:

• tune
• mood