Agnos is a cross-language, cross-platform, lightweight RPC framework with support for passing objects by value or by reference. Agnos is meant to allow programs written in different languages to easily interoperate, by providing the needed bindings (glue-code) and hiding all the details from the programmer. The project essentially serves the same purpose as existing technologies like SOAP, WSDL, CORBA, and others, but takes a minimalistic approach to the issue at hand. Unlike the aforementioned technologies, which tend to require integration with Web servers, using verbose XML-based protocols on top of textual transports (HTTP), often also requiring complex topologies (such as name servers for registering objects, etc.). Agnos is designed to be simple, efficient, and straightforward, allowing for direct communication between two ends using a compact binary protocol.
The X Binary Package System (in short XBPS) is a binary package system designed and implemented from scratch. Its goal is to be fast, easy to use, bug-free, featureful, and portable as much as possible. There is a well documented API provided by the XBPS Library that is the basis for its frontends, to handle binary packages and repositories.
wwwhisper is a privacy-friendly system which simplifies sharing Web resources which are not intended for everyone. It allows you to specify which HTTP resources can be accessed by owners of which email addresses. Mozilla Persona is used to prove that a visitor owns an allowed email address. No site-specific password is needed. The Persona UI makes the authentication process really smooth. wwwhisper is application-independent and can be used for any Web resources.
libKISSlog is a trivial lightweight C++ template library designed and written according to the KISS (Keep It Simple and Straightforward) principle. It leans heavily on STL for keeping its implementation as simple as its usage, and tries to provide C++ developers with a lightweight, paradigm-pure, and flexible alternative to logging libraries which use design and/or implementation decisions which at least the author of libKISSlog believes to be questionable. Its easiest to explain why libKISSlog would be suitable for your needs by listing the things which libKISSlog does not choose to use or do: no singletons or other forms of mutable global state, no macros, no attempt to fit the Java runtime everything model onto a C++ library, no attempt to be a Java-style (bloated) framework, no attempt to make the choice for you of whether you need thread safety, and no compromise on simplicity in order to facilitate questionable inner-loop logging practices.