PSX is a PHP framework for creating RESTful APIs. It helps you to build clean URLs serving Web standard formats like JSON, XML, Atom, and RSS. It includes a handler system that abstracts away SQL queries from domain logic, a routing system that executes correct controller method for the location of the controller and the method annotation, and a flexible data system that converts database records into formats like JSON, XML, Atom, and RSS. A lightweight DI container handles dependencies. The controller supports request and response filters that can modify the HTTP request or response, and filters are provided for Basic and Oauth authentication.

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.

jminix is a simple embeddable restful JMX console. It is useful for when you don't want to use an external full-blown JMX console, but just want to have a simple JMX entry point into your new or existing apps. Embedding JMiniX in a Web app is done simply by declaring a servlet. Deployed as a servlet, it benefits from your Web application configuration such as filters or security constraints.

jmx4py offers a client API for Python similar to the existing Jolokia clients for Perl (jmx4perl), Java, and Javascript. Jolokia is a JMX-HTTP bridge giving an alternative to JSR-160 connectors. It is an agent-based approach with support for many platforms. In addition to basic JMX operations, it enhances JMX remoting with unique features like bulk requests or fine grained security policies. jmx4py builds upon the basic API and offers further features related to monitoring and controlling JVMs via JMX using Python.

RoboZombie allows easy integration with remote services by allowing you to replicate an endpoint contract and generate a proxy to access it.
Contracts can be very flexible in terms of the resources they access. These could be vary from static HTML content or an RRS feed, to a RESTful web service endpoint.
Each endpoint contract is specified on a single interface using annotations to provide the communication metadata. It is then wired into your code via an annotation, where it is created, cached, and injected at runtime.