Crossroads I/O ("libxs") is a library for building scalable and high performance distributed applications. It fits between classic BSD sockets, JMS/AMQP-style message queues, and enterprise message-oriented middleware.
Crossroads I/O extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products, providing an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols, and more.
Crossroads I/O provides a native C API for applications. Support for many more languages is provided by the community through language bindings which can be found at the Crossroads website.
Building and Installation
The following instructions apply to building libxs from an official release
downloaded from the Crossroads I/O website. For building directly from Git,
refer to the
INSTALL file included with the libxs distribution.
On POSIX platforms, libxs uses the standard autotools build system. To build and install the library, ensure your system has a C++ compiler installed, and proceed with the following steps:
maketo build the library.
make checkto run the built in test suite.
make installas root.
On Linux or other platforms which use
ld.sofor dynamic linking, run
ldconfigor equivalent as root to update your system’s shared library cache.
On Windows, solution files for Visual C++ 2010 are provided in the
builds/msvc/ subdirectory of the distribution.
Refer to the
INSTALL file included with the libxs distribution for more
detailed installation instructions.
Crossroads I/O provides a drop-in libzmq compatibility library for ZeroMQ
language bindings and applications. To enable libzmq compatibility, you
must build your copy of libxs with the
--enable-libzmq option to
configure, or on Windows by building the appropriate solution file.
For further details refer to the
doc/xs_zmq.html or the
manual page included with this distribution.
Enabling this option will overwrite any existing installation of
To report a bug, send an email describing your problem to the Crossroads mailing list. To make sure your bug report won’t be missed, you can file a report in the bug tracker.
To help Crossroads developers to fix the bug, please try to provide a minimal test program, ideally written in C, that reproduces the problem you are reporting.
|The bug tracker exists primarily to track bugs and pertinent data (test cases, crash logs, etc.). You should not use it for discussion. In the bug tracker your audience will be very limited. Mailing list serves the purpose of discussing bugs much better.|
Contributing to the Project
Before contributing to the project make sure you understand the legal implications of doing so. These are outlined on the Crossroads I/O website.
To submit your contribution, send it as a patch (using
or similar) to the mailing list. Make sure to use your real name, and prefix
the subject of your post with
All contributions will be reviewed and, if they pass review, accepted. For more details refer to the website.
The libxs development Git tree can be found on Github.
Development is coordinated on the mailing list. Visit the archives to join or view archives of previous discussion.
Extensive documentation is provided with the distribution. Refer to
doc/xs.html, or the
xs(7) manual page after you have installed libxs on
Further resources, language bindings, tutorials, and more can be found on the Crossroads website.
Free use of this software is granted under the terms of the GNU Lesser General
Public License (LGPL). For details see the files
included with the libxs distribution.
As a special exception, the copyright holders of libxs grant you the right
to link the library statically with your software. Refer to the end of
COPYING.LESSER file included with the libxs distribution for details.
: Bug tracker: https://github.com/crossroads-io/libxs/issues
: Legal information: http://www.crossroads.io/dev:legal
: Code review: http://www.crossroads.io/dev:code-review
: Source code: http://github.com/crossroads-io
: Mailing list: email@example.com
: Mailing list archives: http://groups.crossroads.io/
: Project website: http://www.crossroads.io/