HornetQ is a multi-protocol, embeddable, high performance, clustered, asynchronous messaging system. HornetQ is an example of Message Oriented Middleware. It includes an extensive, easy-to-understand user-manual and quick-start guide and over 65 ready-to-run examples out of the box, demonstrating everything from simple JMS usage to complex clusters of servers and more exotic functionality. Its elegant POJO based design has minimal third party dependencies. You can run HornetQ as a stand-alone messaging broker, run it in integrated in your favorite JEE application server, or run it embedded inside your own application. Its journal provides high persistent messaging performance. Automatically switching into native mode when running on Linux, it uses asynchronous IO to provide persistent messaging rates that can saturate the write throughput of a disk. Its pluggable transport system uses JBoss Netty out of the box to provide high performance and scalability on the wire.
Syncless is an experimental, lightweight, non-blocking (asynchronous) client and server socket network communication library implemented in Stackless Python 2.6. It contains an asynchronous DNS resolver (using dnspython) and an HTTP server capable of serving WSGI applications. It aims to be a coroutine-based alternative of event-driven networking engines (such as Twisted and FriendFeed's Tornado). It is already about that fast, but it has fewer features and is less stable now.
libjc is a framework for event-driven development in C. Programs that use it can perform an arbitrary number of operations simultaneously and in the background, and later wait for some or all of them to complete. The source package includes the core library along with a few objects, each of which is able to perform a set of related operations. This framework consumes significantly less memory than standard libraries, and it scales well to multiprocessor systems.
protobuf-rpc-pro is a Java developer library that provides an RPC layer for Google's Protocol Buffer services. It builds upon Netty for low-level NIO. Features include bidirectional RPC calls from client to server and from server to client. The client and server are equal communicating peers. TCP connection re-use / keep-alive, SSL encryption support, RPC call cancellation, timeout and a pluggable logging facility logging RPC call data in Protocol Buffer format are included.
nioReactor is a framework for quickly building scalable event-driven network applications. It is built on top of the Reactor design pattern using NIO sockets. This provides high performance and allows for a complete separation from the application specific code. The goal of the project is to provide a simple set of APIs that allow users to build scalable servers without needing to deal with with the cumbersome and sometimes temperamental peaces of the NIO package.
IRC-API is a stateful, asynchronous IRC API written in Java. It offers an (a)synchronous programming model to its user, and has the ability to save the IRC server state per IRC connection. It supports SSL. The API has been tested on various IRC networks, including EFnet, DALnet, and Undernet. It offers a useful, detailed interface to the Server it connects to.
asyncoro is a Python framework for concurrent distributed network programming with asynchronous completions and coroutines. Asynchronous completions implemented in asyncoro are socket I/O operations (non-blocking sockets), database cursors, sleep timers, and locking primitives. Programs developed with asyncoro have the same logic and structure as Python programs with threads, except for a few syntactic changes. It supports socket I/O notification mechanisms epoll, kqueue, /dev/poll (and poll and select, where necessary), and Windows I/O Completion Ports (IOCP) for high performance and scalability, and SSL for security. asyncoro features include remote execution of coroutines, coroutines monitoring other coroutines, coroutines communicating with messages, message channels etc., for concurrent, distributed, fault-tolerant programming.
AJAPH is an object that can send AJAX requests and process the responses. It supports HTTP GET or POST requests, and synchronous or asynchronous requests with optional parameters. It can set a given page element to an image while waiting for the response. Request responses can be handled as HTML, XML, JSON, or text.