RMIIO is a library that makes it as simple as possible to stream large amounts of data using the RMI framework (or any RPC framework). The RMI framework makes it very easy to implement remote communication between Java programs, yet does not provide any ready solutions for sending large files without blowing out memory on the client or server. What you really want to do is stream data from the client to the server using a framework that does not really expose streaming. The RMIIO library provides some very powerful classes that enable a client to stream data to the server using only a few extra lines of code.
TIDorb Java is a CORBA 2.6 ORB with a high level of stability and performance. It fully implements the Java ORB core and portability APIs, Portable Object Adapter (POA), IIOP protocol (versions 1.0, 1.1, and 1.2), including bi-directional communications, the Dynamic Anys API, DII dynamic invocation interface, and DSI dynamic skeletons APIs, the static invocation API, OBV (object by value passing), and some CORBA messaging QoS policies, and it partially implements RealTime functionalities and Codecs.
Hydro is an independent implementation of ICE, the object-oriented RPC protocol by ZeroC, for the O'Caml programming language. Hydro (like ICE) allows you to bridge language barriers by letting components written in different programming languages communicate with each other. ZeroC's ICE product currently includes implementations for C++, Java, C#, Python, Ruby, VB, and PHP. Hydro adds support for O'Caml. Hydro includes an asynchronous runtime and a generator called hydrogen.
Apache ActiveMQ is a popular and powerful message broker and enterprise integration patterns provider. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy-to-use enterprise integration patterns and many advanced features, while fully supporting JMS 1.1 and J2EE 1.4.
PMS/PyPubSub (short for Python Message Service / Python based Publish Subscribe) is a framework for implementing a publish subscribe mechanism into a Python application. A python process somewhere in the network publishes one or more topics which consist of Python objects. Multiple processes in the network can subscribe to fresh updates of the published topics. A publisher and its subsribers are fully decoupled. The datatype of a topic can be freely defined and changed at runtime. New publishers and subscribers can easily be added at runtime.
j-Interop is a Java Open Source library (under LGPL) that implements the DCOM wire protocol (MSRPC) to enable development of Pure, Bi- Directional, Non-Native Java applications which can interoperate with any COM component. The implementation is itself purely in Java and does not use Java Native Interface (JNI) to provide COM access. This allows the library to be used from any Non-Windows platform. It comes with pre- implemented packages for automation. This includes support for IDispatch, ITypeInfo, and ITypeLib. For more flexibility (in the cases where automation is not supported), it provides an API set to directly invoke operations on a COM server.
The gLite distribution is an integrated set of components designed to enable resource sharing. In other words, this is middleware for building a grid. The gLite middleware is produced by the EGEE project. The distribution model is to construct different services ("node-types") from these components and then ensure easy installation and configuration on the chosen platforms.