fio is an I/O tool meant to be used both for benchmark and stress/hardware verification. It has support for 13 different types of I/O engines (sync, mmap, libaio, posixaio, SG v3, splice, null, network, syslet, guasi, solarisaio, and more), I/O priorities (for newer Linux kernels), rate I/O, forked or threaded jobs, and much more. It can work on block devices as well as files. fio accepts job descriptions in a simple-to-understand text format. Several example job files are included. fio displays all sorts of I/O performance information, including complete IO latencies and percentiles. Fio is in wide use in many places, for both benchmarking, QA, and verification purposes. It supports Linux, FreeBSD, NetBSD, OS X, OpenSolaris, AIX, HP-UX, and Windows.
NanoHttpd is a lightweight HTTP server designed for embedding in other applications. It's only one Java file, in two "flavors", one strictly Java 1.1 compatible, and one at "current" standards. It supports GET, POST, PUT, HEAD and DELETE requests, and supports file uploading with very small memory overhead. Temp file usage and the threading model are easily customized.
Yate is a next-generation telephony engine. While currently focused on Voice over Internet Protocol (VoIP) and PSTN, its power lies in its ability to be easily extended. It supports SIP, H.323, IAX, MGCP, Jingle, Jabber, E1, T1, analogic, robbed bit, ISDN PRI, BRI, and SS7. YateClient is an Instant Messenger and Voice application for Jabber/Jingle IM, SIP, H.323, and IAX VoIP protocols.
Quassel IRC is a modern, cross-platform, distributed IRC client, meaning that one or more clients can attach to and detach from a central core, much like the popular combination of screen and a text-based IRC client, but graphical. In addition to this unique feature, it aims to be a comfortable chatting program.
CRest (Client REST) is a lightweight library that simplifies the integration of third party RESTful services into Java applications. CRest is mainly annotation-driven, allowing the developer to focus on the essential aspects of the integration of a REST service, such as the definition of the Java interface that maps the remote REST methods and the data model the interface will deal with. The rest is achieved by annotating a plain Java interface with the relevant information such as the service end-point, the desired timeouts, URL formats, etc. CRest will handle everything else, including HTTP request generation, auto marshalling of the response, and more.