ejabberd 2.1.0 now supports XEP-0227, a.k.a. PIEFXIS for Portable Import/Export Format for XMPP-IM Servers.

In the first articles of this series, we learned how to use the exmpp API and how to use it to write a simple external XMPP component.

In this last installment we will complete our component, making it aware of the presence status of our users.

The source code for this article can be downloaded from web_status_v2.tar.gz.

ProcessOne's offering includes transports under the commercial name IMgateways.

It takes the form of an ejabberd component on the server-side. It enables the users to simply interact in their Jabber/XMPP client with third party IM systems, in the very same way they use it everyday.

The internet of things (or "IoT" for short) has come to describe a number of technologies and research disciplines that enable the internet to reach out into the world of physical objects.

IMgateways package offers an easy way to deploy high-end professional transport for third party networks in five minutes.

Our Twitter gateway service for XMPP, Tweet.IM has been updated.

In part I we focused on learning the basic of the exmpp API.

In this second part we start to think about how one can use the the learned API to write and deploying XMPP components.

The source code for this article can be downloaded from web_status.tar.gz.

ProcessOne has released the second beta of ejabberd 2.1.0.

ejabberd has gained a STUN server, helping Jingle communications.

Introducing EXMPP

In this series of articles we will introduce exmpp, the long awaited high-performance XMPP library for erlang, released by ProcessOne weeks ago. While doing so, we will learn how to use the library to build a highly scalable XMPP bot. As a library, exmpp is oriented towards high performance and low memory usage, while being general enough to be useful in different scenarios (clients, servers, components).

In this first installment we will learn the basis of exmpp, and start with our bot implementation.