Channel is a C++ template framework for distributed message passing and event dispatching. Its major components (message IDs, routing algorithms...) are highly configurable as template parameters. As a namespace shared by peer threads, channels support publish/subscribe scope control, message filtering, and translation.
nexB OpenAssets is a tool for inventorying, managing, and monitoring applications, software, hardware, networks, and generally any IT asset. It is designed so that system administrators, IT, and finance can determine what they have, how it is configured, what it is used for, and how much it is being used, so that informed decisions can be made. It complements existing network management software, integrates with a growing number of protocols and tools, and features no-agent discovery and inventory, configuration management including dependencies and correlation, monitoring, and reporting. It makes extensive and innovative use of XML, Xpath, and Xquery.
The PEAK library tries to achieve high performance in combining multi-threading with an efficient I/O event model. You can write event-based applications that use massive sockets I/O, timers, and signals. Its underlying I/O multiplexing engine supports kqueue(2) (FreeBSD, NetBSD, and Mac OS X), epoll(2) (Linux 2.6), and /dev/poll (Solaris). It provides support for optimized memory allocations, basic database primitives, and synchronization.
ZooLib allows one to write a single set of C++ sources which can be compiled into native executables for Mac OS, Windows, BeOS, or POSIX-compliant systems that use the X Window system (such as Linux). Zoolib provides a GUI toolkit with a uniquely flexible layout system. It also provides a single-file database format, TCP networking, and extensive debugging support. ZooLib applications are multithreaded. ZooLib requires only minimal support from the underlying OS and platform GUI layer, and thus could be ported to a completely new platform without too much difficulty. ZooLib is fully production quality on Windows and MacOS, completely implemented but untested on BeOS, and not yet complete on POSIX. Please note that the sources from the "demo" branch are also required to build ZooLib or to get started writing your own ZooLib applications.