Free rpc software for linux

Major Features:

1. Simple, pythonic API.
2. Support for Django authentication.
3. Mostly supports JSON-RPC 1.1 spec.
4. Proxy to test your JSON Service.

Requirements:

• Python

Vortex Library is a BEEP Core protocol implementation, following the standard definitions in RFC 3080 and RFC 3081.
Vortex Library has a clean and easy-to-use API that allows you to write new protocols or user applications.
Vortex Library has been developed within the Af-Arch project, and it is being used at the data transport layer. However, Vortex Library can be used independently of Af-Arch.
Currently Vortex Library is supported in all Microsoft Windows Platforms as well as Linux.
Enhancements:
- A general update was done to make this release more usable on Microsoft Windows, using Visual Studio compilers.
- Missing support was added to enable getting error codes reported by peer at channel creation.
- Now xml-rpc-gen is able to include user code into the IDL definition that is placed at the resulting XML-RPC server.

RPC::pClient is a Perl extension for writing pRPC clients.

SYNOPSIS

use RPC::pClient;

$sock = IO::Socket::INET->new(PeerAddr => joes.host.de,
PeerPort => 2570,
Proto => tcp);

$connection = new RPC::pClient(sock => $sock,
application => My App,
version => 1.0,
user => joe,
password => hello!);

pRPC (Perl RPC) is a package that simplifies the writing of Perl based client/server applications. RPC::pServer is the package used on the server side, and you guess what RPC::pClient is for. See RPC::pClient(3) for this part.
pRPC works by defining a set of of functions that may be executed by the client. For example, the server might offer a function "multiply" to the client. Now a function call

@result = $con->Call(multiply, $a, $b);

on the client will be mapped to a corresponding call

multiply($con, $data, $a, $b);

on the server. (See the funcTable description below for $data.) The function calls result will be returned to the client and stored in the array @result. Simple, eh?

Client methods

new

The client constructor. Returns a client object or an error string, thus you typically use it like this:

$client = RPC::pClient->new ( ... );
if (!ref($client)) {
print STDERR "Error while creating client object: $clientn";
} else {
# Do real stuff
...
}

Call

calls a function on the server; the arguments are a function name, followed by function arguments. It returns the function results, if successfull. After executing Call() you should always check the error attribute: An empty string indicates success. Thus the equivalent to

$c = Add($a, $b)
# Use $c
...

is

$c = $client->Call("Add", $a, $b);
if ($client->error) {
# Do something in case of error
...
} else {
# Use $c
...
}

CallInt

Similar to and internally used by Call. Receives the same arguments, but the result is prepended by a status value: If this status value is TRUE, then all went fine and the following result array is valid. Otherwise an error occurred and the error message follows immediately after the status code. Example:

my($status, @result) = $client->CallInt("Add", $a, $b);
if (!$status) {
# Do something in case of error
my $errmsg = shift @result || "Unknown error";
...
} else {
...
}

Encrypt

This method can be used to get or set the cipher attribute, thus the encryption mode. If the method is passed an argument, the argument will be used as the new encryption mode. (undef for no encryption.) In either case the current encryption mode will be returned. Example:

# Get the current encryption mode
$mode = $server->Encrypt();

# Currently disable encryption
$server->Encrypt(undef);

# Switch back to the old mode
$server->Encrypt($mode);

nessquik is a fast Web-based Nessus scanner that is intended to replace the Nessus stand alone client.
nessquik project uses the prototype.js library to provide a responsive interface even when dealing with all of the available Nessus plugins.
Enhancements:
- A complete redesign of the interface has been done.
- Much more flexibility has been added to the interface as well.
- Scans can be stopped while they are running.
- All scan settings can be configured at creation time.
- An XML-RPC API has been added for third party developers.
- Numerous code fixes and performance enhancements have been made to every part of the system.

Project Steve Guttenberg allows you to create an online journal or "blog" with a minimum amount of hassle. PSG doesnt take control of your website. Project Steve Guttenberg project doesnt have a massive list of dependencies, such as a database server.
Main features:
- Multiple users
- Rich RSS 2.0 syndication feed including tags and Dublin Core metadata
- User, tag and keyword searching, with RSS output for such searches
- XML-RPC ping support for use with weblogs.com, Technorati and blo.gs
- Support for sending and receiving TrackBacks
- Support for RSS enclosures and file uploads, so you can do podcasting
- Support for gravatar avatars on comments
Enhancements:
- This release adds support for captchas and the akismet comment spam service, a new asset manager, support for Googles ping server, and an updated French translation.

XML::DB::DatabaseManager is an approximation to the XML:DB DatabaseManager.

SYNOPSIS

use XML::DB::DatabaseManager;
my $driver = Xindice; my $url = http://localhost:4080;
eval{ $dbm = new XML::DB::DatabaseManager(); $dbm->registerDatabase($driver); $col = $dbm->getCollection("xmldb:$driver:$url/db/test"); ...... };
if ($@){ die $@; }
deregisterDatabase($driver);

This is the initial class to use to get access to the XML:DB modules, an approximate implementation of the XML:DB API defined for Java at http://www.xmldb.org. This implementation is designed to give a uniform Perl access over XML-RPC to both of the current free native XML databases, eXist and Xindice, as well as providing the same front-end for a plain file-system.

Unlike the DatabaseManager defined in the XML:DB API (which is a Factory), this simply registers driver names, generating a new Database instance for each request. Multiple database drivers can be used simultaneously (eg. to transfer data from one database to another). The drivers themselves are rather confusingly called Databases in this system.

Only one DatabaseManager can be instantiated in a program.

idl2pysrv is a IDL compiler to Python RPC-GIOP skeleton server.

SYNOPSIS

idl2pysrv [options] spec.idl

OPTIONS

All options are forwarded to C preprocessor, except -h -i -J -v -x.

With the GNU C Compatible Compiler Processor, useful options are :

-D name
-D name=definition
-I directory
-I-
-nostdinc

Specific options :

-h

Display help.

-i directory

Specify a path for import (only for version IDL 3.0).

-J directory

Specify a path for Python package.

-v

Display version.

-x

Enable export (only for version IDL 3.0).

idl2pysrv parses the given input file (IDL) and generates :

a set of Python sources : an optional _spec_skel.py and pkg_skel/__init__.py for each package

setup_skel.py

idl2pysrv is a Perl OO application what uses the visitor design pattern. The parser is generated by Parse::Yapp.

idl2pysrv needs a cpp executable.

Boxtream is both an audio and video encoder and streamer and an assembly of audio and video hardware, forming a mobile video streaming studio.

It is designed to easily record and stream live presentations including a presenter and synchronized slides, or slides only, or presenter only, and was built to stream live courses over the Internet for distance learning students. It supports Extron video switchers (Kramer support is planned).

The project can be entirely controlled remotely over XML-RPC, and includes an X11 interface built with wxWidgets. It supports five different streaming scenarios. The software can still be used without most of the hardware included in the original boxtream project.