NFSv4 specifies that the RPC calls be batched into a "compound" call. There is no support for this in RPCGEN. By rearranging the ONC IDL for NFSv4 into AutoGen definitions, these templates will emit the original IDL *plus* all the code to package, send, distribute, collect, return, and dispatch the results. The distributed program author merely needs to call and supply server procedures for the routines specified in the IDL. Templates for these calls and service routines is provided, too. The NFSv4 definitions are included.
MinML-RPC is an implementation of XML-RPC server written in Java. It was designed to be used in embedded systems where storage space is at a premium. The code is quite compact, and it was also designed to minimize the heap space used by the program when executing a procedure call. The distribution includes the parser, the XML-RPC server implementation, and a small, high-performance HTTP 1.1 server.
RabbIt is a mutating, caching Web proxy used to speed up surfing over slow links like modems. It does this by removing advertising and background images and scaling down images to low quality JPEGs. RabbIT is written in Java and should be able to run on any platform. It does depend upon an image converter if image scaling is on. The recommended image converter is "convert" from the ImageMagick package.
RUE is intended to be used as a general, local or remote, monitoring tool for any Java based server such as Tomcat, Tyrex, Enhydra, JBoss, JOnAS, etc. RUE is written in 100% Java, and features pluggable samplers and sensors, data visualization plug-ins, configurable data history, output of HTML reports, a standard AWT GUI, JNDI-based sensor lookups, and a simple API for pooling, aggregation, and averaging.
uIP is probably the smallest implementation of the TCP/IP protocol stack ever written in a high level language; the code footprint is on the order of a few kilobytes and RAM usage is on the order of a few hundred bytes. uIP is intended to be used in embedded systems running low end 8- and 16-bit microcontrollers.
JXTA technology is a set of open protocols that allow any connected device on the network ranging from cell phones and wireless PDAs to PCs and servers to communicate and collaborate in a P2P manner. JXTA peers create a virtual network where any peer can interact with other peers and resources directly even when some of the peers and resources are behind firewalls and NATs or are on different network transports. The project goals are interoperability across different peer-to-peer systems and communities, platform independence, multiple/diverse languages, systems, and networks, and ubiquity: every device with a digital heartbeat.