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.
libnode is a C++ implementation of Node.js. Just like Node.js, libnode provides non-blocking I/O, which enables you to develop scalable Web applications in C++. The memory management of libnode is automatic, based on either shared_ptr or bdw-gc. libnode is good to use on embedded devices because its system resource consumption is lower than Node.js.
blists is a Web interface to mailing list archives. It works off indexed mbox files. It includes two programs: bindex and bit. bindex generates or updates the index file (incremental updates are supported). bit is a CGI/SSI program that generates Web pages on the fly. Both programs are written in C and are very fast.
JGame Flash is an ActionScript 3 port of the JGame 3.5 API. It can be compiled with the free Flex toolkit. A Java-AS3 translator is included to make porting games easier. The goal of this project is to eventually enable JGame Java games to be converted (partially) automatically to ActionScript 3. JGame Flash works on Android Flash 10.1 and supports accelerometer input.
Flixn Media Platform is a collection of Flash-based tools and backend utilities to facilitate the generation of rich Web media, and video in particular. It features components to enable recording from a webcam and/or microphone, uploading and transcoding of video, and feature-rich playback. The platform was designed for mass/virtual deployment.
Huxley is a set of classes that makes it trivial to produce legitimate output for queries made by the prevailing standard of REST queries. Instead of writing a network API with many methods, being run over RPC, you instead write only a couple of methods that are accessed by HTTP GET requests. You then return the results (in either XML, JSON, or text) for processing. XML and JSON are chosen because of the ease by which they can be parsed by most languages. In this way, you open up the scope of your network services to many more people than would otherwise have access to it.