Free rpc software for linux

Aranha is an application that uses an XML-RPC layer to retrieve information from one or more servers. The type of information gathered is implemented via plugins, and can be displayed or archived in several different ways.

The data is gathered in Round Robin Databases (integrated with rrdtool) and can be accessed using a XUL interface available from the system. Plugins are very easy to write.

Configuration

To configure this module, either pass specific configuration values to
Makefile.PL like this:

perl Makefile.PL CONFIG_VAR="config val"
or
edit the %DEFAULTS variable on the toplevel Makefile.PL

Installation

To install this module type the following:

perl Makefile.PL
make
make test
make install

CamRPC is a simple client/server solution to update/manage several webcams using a PHP enabled Web server and any client with XML-RPC capabilities.
Enhancements:
Server
- A web server (Apache tested, http://httpd.apache.org/)
- PHP 4 >= 4.1.0 with XML module
- php XML-RPC (http://xmlrpc.usefulinc.com/, included 1.1.1 in the package)
- A directory with write enabled for the httpd daemon
Client
- Your image grabber of choice
- Python client: python 2 >= 2.2
- Perl client: Frontier::RPC, MIME::Base64 and MIME::Types
Enhancements:
- updated included xml-rpc lib due SA15852: http://secunia.com/advisories/15852/
- Now camrpc is distributed with xml-rpc 1.1.1.

Nanoserv is a sockets daemon toolkit for PHP 5.1+
It is distributed under the terms of the GNU Lesser General Public License.
Its a complete rewrite of the shadok sockets PHP4 library (the one behind phpos and sh4re).
Main features:
- 100% object oriented
- native support for TCP with SSL/TLS and UDP connections
- multiplexing and forking listeners
- handlers for raw connections, line input, HTTP, SMTP, XML-RPC, Syslog, ...
- transparent inter process communications with forked handlers
- and probably more ...
Most of the features work with PHP 5.0 but you will need PHP 5.1+ to take advantage of the shared objects and crypto support.

FreeMED is a Web-based medical records (EMR) and patient management system with a printing system, patient scheduling, an HL7 interface, a billing system, XML-RPC Web services, and many other features.

It has an extensible modular architecture, allowing it to be customized based on individual practices without having to rewrite core components of the system. It is HIPAA compliant.

FreeMED LiveCD 0.1 is based on the Kubuntu 5.04 (Hoary) Live CD.

Kenosis is a fully-distributed p2p RPC system built on top of XMLRPC. Nodes are automatically connected to each other via a Kademlia-style network, and can route RPC requests efficiently to any online node. Kenosis project is reliable and well-tested.
- Nodes are identified by 160-bit addresses.
- Nodes can find other nodes given an address and can find the set of nodes with addresses nearest to a given address.
- Nodes can route RPC requests efficiently to any online node.
Kenosis is zero-defect software
Too many peer-to-peer programs and libraries have initially seemed to work but floundered under increasing complexity. One of our goals for kenosis was to make reliable software that would Just Work.
Every line of Kenosis has been subjected to extensive unit testing and simulation testing.
- Kenosis is designed from the ground up for simplicity, stability, and scalability.
- Kenosis does one thing and does it well. It is our hope that others will use Kenosis as a foundation for new and exciting peer-to-peer applications.
Compatibility
Kenosis must work on a wide range of platforms because we want it to provide a solid basis for many p2p applications.
- Kenosis is written in pure python
- Kenosis has been tested on Windows, Mac OS X, and Linux.
- Kenosis works in almost any networking environnment, including restrictive corporate firewalls, because it uses XMLRPC for its network communications. It can also work with an HTTP proxy.
Enhancements:
- This release fixes bugs that prevented the client from bootstrapping from other nodes.

mod_xmlrpc_auth is an Apache module for XML-RPC Authentication.

mod_xmlrpc_auth is an Apache module which performs authentication and authorization using an XML-RPC call.

Installation:

To build mod_xmlrpc_auth, you should be able to simply run these commands:

./configure
make
make install

Encap Package Support

To build this software as an Encap package, you can pass the --enable-encap option to configure. This will be automatically enabled if the epkg or mkencap programs are detected on the system, but can be overridden by the --disable-encap option.

When building an Encap package, the configure script will automatically adjust the installation prefix to use an appropriate Encap package directory. It does this using a heuristic algorithm which examines the values of the ${ENCAP_SOURCE} and ${ENCAP_TARGET} environment variables and the argument to configures --prefix option.

If mkencap was detected on the system, it will be automatically run during "make install". By default, epkg will also be run, but this can be inhibited with the --disable-epkg-install configure option.

For information on the Encap package management system, see the WSG Encap Archive:

http://www.encap.org/

Configuration

For configuration information, please see the mod_xmlrpc_auth.conf file.

eCryptfs is an POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux. eCryptfs is derived from Erez Zadoks Cryptfs, implemented through the FiST framework for generating stacked filesystems.
eCryptfs extends Cryptfs to provide advanced key management and policy features. eCryptfs stores cryptographic metadata in the header of each file written, so that encrypted files can be copied between hosts; the file will be decryptable with the proper key, and there is no need to keep track of any additional information aside from what is already in the encrypted file itself. Think of eCryptfs as a sort of ``gnupgfs.
eCryptfs is a native Linux filesystem (other popular cryptographic filesystems for Linux require FUSE or operate via RPC calls). It can be built and distributed as a stand-alone kernel module for the Linux kernel version 2.6.15 or higher; there is no need to apply any kernel patches.
Enhancements:
- Legacy releases of eCryptfs.

Apache XML-RPC is a Java implementation of XML-RPC, a popular protocol that uses XML over HTTP to implement remote procedure calls.
Apache XML-RPC was previously known as Helma XML-RPC.
If you have code using the Helma library, all you should have to do is change the import statements in your code from helma.xmlrpc.* to org.apache.xmlrpc.*.
Apache XML-RPC provides two client classes.
1. org.apache.xmlrpc.XmlRpcClient uses java.net.URLConnection, the HTTP client that comes with the standard Java API
2. org.apache.xmlrpc.XmlRpcClientLite provides its own lightweight HTTP client implementation.
If you need full HTTP support (e.g. Proxies, Redirect etc), you should use XmlRpcClient. If you dont need full HTTP support and are concerned about performance, you should experiment with both XmlRpcClient and XmlRpcClientLite.
On some platforms XmlRpcClient may be faster, while on others XmlRpcClientLite may be faster. Both client classes provide the same interface, which includes methods for synchronous and asynchronous calls.
Enhancements:
- Version 3 is a complete rewrite of version 2.
- It introduces the concept of vendor extensions: by default, client and server are completely compliant to the XML-RPC specification.
- However, the user may enable certain non-standard features: streaming mode, support for all primitive Java types, nulls, DOM elements, JAXB objects, Serializable instances, and so on.
- Even more, the user may specify custom datatypes.