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

SYNOPSIS

use DCE::RPC; use Authen::Perl::NTLM qw(lm_hash nt_hash);
use constant DCOM_IREMOTEACTIVATION => pack("H32", "B84A9F4D1C7DCF11861E0020AF6E7C57");
use constant DCOM_IF_VERSION => 0x00;
use constant DCOM_XFER_SYNTAX => pack("H32", "045D888AEB1CC9119FE808002B104860");
use constant DCOM_XFER_SYNTAX_VERSION => 0x02;

$passwd = "passwd";
$lm_hpw = lm_hash($passwd);
$nt_hpw = nt_hash($passwd);
$ntlm = new_client Authen::Perl::NTLM($lm_hpw, nt_hpw);
$rpc_host = "www.rpc.com";
$rpc_port = 135;
$rpc = new DCE::RPC($rpc_host, $rpc_port, $ntlm);
$bind_msg = $rpc->rpc_bind_ack_resp(1, DCOM_IREMOTEACTIVATION, DCOM_IF_VERSION,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));
$request_msg = $rpc->rpc_co_request("Hi, there! This is Stub!", 1, 0x0e, DCOM_IREMOTEACTIVATION, "Authentication Credentials");
$response_msg = $rpc->rpc_request_response($request_msg);
$alt_ctx_msg = $rpc->rpc_alt_ctx(1, DCOM_IREMOTEACTIVATION . DCOM_IF_VERSION
,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));

The DCE RPC protocol is an application level protocol from OpenGroup that allows applications to do Remote Procedure Calls. It is the underlying wire protocol for DCOM (Distributed Common Object Model) by Microsoft.
This module was motivated by an reverse-engineering effort on a DCOM client. Therefore, functions that are implemented gear more toward client side implementation. Also, the initial version only supports Connection Oriented version of DCE RPC. It also assumes NTLMSSP as the underlying authentication protocol. This can change based on the input of the users of this modules.

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);

JSON-RPC-Java provides an RPC implementation that allows JavaScript DHTML Web applications to call remote methods in a Java Application Server (AJAX functionality) without the need for page reloading.
JSON-RPC-Java library is an enabler for the next generation of fast and highly dynamic enterprise Java Web applications. Minimal changes (if any) are necessary to existing server-side Java code to allow calling from JavaScript (such as the marshalling and unmarshalling of special types), as JSON-RPC-Java dynamically maps JavaScript objects to and from Java objects using Java reflection.
Enhancements:
- The license has changed from the LGPL to the Apache License, Version 2.0.
- New object registration, lookup, and unregister APIs have been added to JSONRPCBridge.

RPC::XML::Procedure is an object encapsulation of server-side RPC procedures.

SYNOPSIS

require RPC::XML::Procedure;

...
$method_1 = RPC::XML::Procedure->new({ name => system.identity,
code => sub { ... },
signature => [ string ] });
$method_2 = RPC::XML::Procedure->new(/path/to/status.xpl);

IMPORTANT NOTE

This package is comprised of the code that was formerly RPC::XML::Method. The package was renamed when the decision was made to support procedures and methods as functionally different entities. It is not necessary to include both this module and RPC::XML::Method -- this module provides the latter as an empty subclass. In time, RPC::XML::Method will be removed from the distribution entirely.

The RPC::XML::Procedure package is designed primarily for behind-the-scenes use by the RPC::XML::Server class and any subclasses of it. It is documented here in case a project chooses to sub-class it for their purposes (which would require setting the method_class attribute when creating server objects, see RPC::XML::Server).

This package grew out of the increasing need to abstract the operations that related to the methods a given server instance was providing. Previously, methods were passed around simply as hash references. It was a small step then to move them into a package and allow for operations directly on the objects themselves. In the spirit of the original hashes, all the key data is kept in clear, intuitive hash keys (rather than obfuscated as the other classes do). Thus it is important to be clear on the interface here before sub-classing this package.

XML-RPC Client/Server C Library is a cross-platform software written in C that supports persistent HTTP/1.1 conenctions over SSL and comes with XML-RPC interface description language and client/server code compiler. Libxr depends on glib2 and libxml2.
Main features:
- Persistent connections over HTTP/1.1
- SSLv3/TLSv1 using OpenSSL.
- XML-RPC interface description language (XDL).
- XML-RPC client stubs/servlet skels compiler.
- Multiple servlets per server.
- Servlet lifetime (init -- call -- call -- fini).
- Multiplatform (linux, mingw32 on windows).
- IPV6 as soon as OpenSSL 0.9.9 is released.

XML-RPC project is a lightweight standard, enabling RPC over HTTP by using XML as a marshaling format.

REBOL project is a scripting language (architected mainly by Carl Sassenrath of Amiga fame).

rebXR brings these two great flavors together, making REBOL a first-class citizen of XML-RPC land.