Skip to main content

Working with Xmpp in Python

Xmpp is an open standard for messaging and presence, used for instant messaging systems. It is also used for chat systems in several games, most notably League of Legends made by Riot Games.

Xmpp is an xml based protocol. Normally you work with xml documents - with Xmpp you work with a stream of xml elements, or stanzas - see for the full definitions of these concepts. This has some implications on how best to work with the xml.

To experiment with Xmpp, let's start by installing a chat server based on Xmpp and start interacting with it. For my purposes I've chosen Prosody - it's nice and simple to install, especially on macOS with Homebrew:

brew tap prosody/prosody
brew install prosody

Start the server with prosodyctl - you may need to edit the configuration file (/usr/local/etc/prosody/prosody.cfg.lua on the Mac), adding entries for prosody_user and pidfile. Once the server is up and running we can start poking at it to get a feel for how to work with the Xmpp protocol. For the purposes of this demonstration we also need to relax some common sense security requirements, to allow authentication over unencrypted connections.

Add the following to the configuration file, at the top:

prosody_user = "<your user name>"
pidfile = ""
allow_unencrypted_plain_auth = true

Then start the Prosody server from a terminal window:

prosodyctl start

You should see log output from the server, indicating that has activated host localhost and is listening on port 5222.

Before we can do much with this chat server we need to add a user:

prosodyctl adduser me@localhost

I would also recommend trying it out with an existing chat client - I like Swift, primarily for its debug console. Once you've verified that the server is working, we can start experimenting with talking to it on a lower level.

Communicating in Python

Let's do some experiments from a Python terminal. First, let's open a socket to talk to the server in Python:

import socket
s = socket.socket()
s.connect(("localhost", 5222))
start = "<?xml version='1.0'?>" \
"<stream:stream to='localhost' version='1.0' " \
"xmlns='jabber:client' " \

Assuming everything is working correctly you should get output like this (minus the formatting):

<?xml version='1.0'?>
        <mechanisms xmlns=urn:ietf:params:xml:ns:xmpp-sasl>
    <auth xmlns=>
    <starttls xmlns=urn:ietf:params:xml:ns:xmpp-tls/>

This is the start of the handshake between the client and the server that takes place when the client wants to connect. That initial message we send to the server informs it we want to establish a connection - it responds with a stream:features element listing the possible authentication mechansims. It also indicates that it can provide a secure connection, with the presence of the starttls element.

While a proper Xmpp client should use a secure authentication mechanism and use a secure connection, we’ll ignore that for now and use the PLAIN authentication. If you don’t see that in your output you need to revisit the configuration of the server to allow it.

The next step in the handshake is to authenticate, sending the userid and password. For the PLAIN mechanism the userid and password are encoded into a BASE64 string:

import base64
key=base64.b64encode("\0{0}\0{1}".format("me", "test").encode("ascii")).decode()

Then we send an auth element to the server:

package = "<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN'>{0}</auth>".format(key)

We should see a confirmation from the server that the authentication was successful:

<success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'></success>

The next bit feels somewhat strange, but it still makes sense. We send the stream element again - exactly the same as we did in the beginning:


We get a similar response, listing features:

<?xml version='1.0'?>
    <c hash='sha-1'
    <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
    <session xmlns='urn:ietf:params:xml:ns:xmpp-session'>
    </session><ver xmlns='urn:xmpp:features:rosterver'/>

This tells us that bind is required, that is binding this connection to a resource id. This is to identify different connections for the same user from different chat clients. The bind is done with an iq element:

bind="<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'><resource>test</resource></bind>"
iq="<iq id='id1' type='set' from='me@localhost'>{0}</iq>".format(bind)

Finally we announce our presence:


At this point things are getting too complicated to do anything meaningful from the Python terminal - we need to start writing a proper Python program.


Popular posts from this blog

Mnesia queries

I've added search and trim to my expiring records module in Erlang. This started out as an in-memory key/value store, that I then migrated over to using Mnesia and eventually to a replicated Mnesia table. The fetch/1 function is already doing a simple query, with match_object. Result=mnesia:match_object(expiring_records, #record{key=Key, value='_', expires_at='_'}, read) The three parameters there are the name of the table - expiring_records, the matching pattern and the lock type (read lock). The fetch/1 function looks up the key as it was added to the table with store/3. If the key is a tuple, we can also do a partial match: Result=mnesia:match_object(expiring_records, #record{key= {'_', "bongo"}, value='_', expires_at='_'}, read) I've added a search/1 function the module that takes in a matching pattern and returns a list of items where the key matches the pattern. Here's the test for the search/1 function: search_partial_…

Replicated Mnesia

I'm still working on my expiring records module in Erlang (see here and here for my previous posts on this). Previously, I had started using Mnesia, but only a RAM based table. I've now switched it over to a replicated disc based table. That was easy enough, but it took a while to figure out how to do, nonetheless. I had assumed that simply adding ... {disc_copies, [node()]} ... to the arguments to mnesia:create_table would be enough. This resulted in an error: {app_test,init_per_testcase, {{badmatch, {aborted, {bad_type,expiring_records,disc_copies,nonode@nohost}}}, ... After some head-scratching and lots of Googling I realized that I was missing a call to mnesia:create_schema to allow it to create disc based tables. My tests for this module are done with common_test so I set up a per suite initialization function like this: init_per_suite(Config) ->mnesia:create_schema([node()]), mnesia:start(…

Optimizing Wine on OS X

I've been doing some performance analysis of EVE running under Wine on OS X. My main test cases are a series of scenes run with the EVE Probe - our internal benchmarking tool. This is far more convenient than running the full EVE client, as it focuses purely on the graphics performance and does not require any user input.

Wine Staging One thing I tried was to build Wine Staging. On its own, that did not really change anything. Turning on CSMT, on the other hand, made quite a difference, taking the average frame time down by 30% for the test scene I used. While the performance boost was significant there were also significant glitches in the rendering, with parts of the scene flickering in and out. Too bad - it means I can't consider this yet for EVE, but I will monitor the progress of this. OpenGL Profiler Apple has the very useful OpenGL profiler available for download. I tried running one of the simpler scenes under the profiler to capture statistics on the OpenGL calls mad…