18 releases (9 breaking)

0.17.0 Jun 27, 2022
0.16.1 Jan 17, 2022
0.16.0 May 8, 2021
0.15.0 Oct 19, 2020
0.8.3 Nov 7, 2017

#323 in Network programming

Download history 36/week @ 2022-10-08 12/week @ 2022-10-15 14/week @ 2022-10-22 34/week @ 2022-10-29 36/week @ 2022-11-05 25/week @ 2022-11-12 24/week @ 2022-11-19 11/week @ 2022-11-26 19/week @ 2022-12-03 62/week @ 2022-12-10 21/week @ 2022-12-17 20/week @ 2022-12-24 6/week @ 2022-12-31 14/week @ 2023-01-07 23/week @ 2023-01-14 37/week @ 2023-01-21

84 downloads per month
Used in vigil-server


3.5K SLoC



See full documentation


Add this to your Cargo.toml:

libstrophe = "0.17.0"

Build Status

libstrophe - ergonomic wrapper for Rust

This library provides high level ergonomic bindings for libstrophe, an XMPP client library.


The documentation for this library covers only Rust specific bits and refers to original library documentation in most other cases.


The general workflow is quite similar to what you get with the C library. The topmost object is Context. It contains platform-specific bits like logging and memory allocation. Plus an event loop used to keep things going. This crate wraps logging with the facilities provided by log crate (provided the default rust-log feature is enabled). Memory allocation is also handled by Rust native means. When a Connection is created it will temporarily consume the Context. After all of the setup is done, call one of the connect_*() methods to retrieve the Context back. In this manner a single Context can be used for multiple Connections consequently. When you're done with setting up Connections for the Context, use run() or run_once() methods to start the event loop rolling.


This create tries to be as safe as possible. Yet it's not always possible to guarantee that when wrapping a C library. The following assumptions are made which might not necessary be true and thus might introduce unsafety:

  • Context event loop methods are borrowing self immutably considering it immutable (or more specifically having interior mutability)

The main objects in this crate are marked as Send and it should be indeed be safe to send them between threads. Yet, no major investigation of the library source code has been performed to ensure that this is true.

Initialization and shutdown

You don't need to call the initialization function, it's done automatically when creating a Context. Yet you might want to call the shutdown() function when your application terminates. Be aware though that the initialization can be called only once in the program lifetime so you won't be able to use the library properly after you called shutdown().


The crate has the ability to store callbacks taking ownership of them so you can pass closures and not care about storing them externally. There are some things to note about it though. It's not always possible to know whether the underlying library accepted the callback. The crate will keep the closure internally in either case, though it may not ever be called by the library. You can still remove the callback with the corresponding *handler_delete() or *handler_clear() method.

Due to the way the the C libstrophe library is implemented and how Rust optimizes monomorphization, your callbacks must actually be compiled to different function with separate addresses when you pass them to the same handler setup method. So if you want to pass 2 callbacks hander_add ensure that their code is unique and rust didn't merge them into a single function behind the scenes. You can test whether 2 callbacks are same or not with the Connection::*handlers_same() family of functions. If it returns true than you will only be able to pass one of them to the corresponding handler function, the other will be silently ignored.

Due to the fact that the crate uses userdata to pass the actual user callback, it's not possible to use userdata inside the callbacks for your own data. So if you need to have a state between callback invocations you must use closures.

Because the main objects are marked as Send and we store callbacks inside them, all callbacks must also be Send.


let connection_handler = |ctx: &libstrophe::Context,
                          _conn: &mut libstrophe::Connection,
                          _evt: libstrophe::ConnectionEvent| {

let ctx = libstrophe::Context::new_with_default_logger();
let mut conn = libstrophe::Connection::new(ctx);
let ctx = conn.connect_client(None, None, connection_handler).unwrap();

For more complete examples see this crate src/examples directory and libstrophe examples.

Crate features

The following features are provided:

  • rust-log - enabled by default, makes the create integrate into Rust logging facilities
  • libstrophe-0_9_3 - enabled by default, enables functionality specific to libstrophe-0.9.3
  • libstrophe-0_10_0 - enabled by default, enables functionality specific to libstrophe-0.10.0
  • libstrophe-0_11_0 - enabled by default, enables functionality specific to libstrophe-0.11.0

License: LGPL-3.0