Free rpc inc software for linux

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.

Porcupine is a web application server that provides an object oriented framework for developing web applications rapidly.

Many of the tasks required for building web applications as you know them, are either eliminated or simplified. For instance, when developing a Porcupine application you dont have to design a relational database. You only have to design and implement your business objects as classes, using the building blocks provided by the framework (datatypes). Porcupine integrates a native object database, no mapping required.

Another tedious task for web applications is the interface design, and the constraints imposed by HTML. QuiX, the servers integrated XUL motor, simplifies the interface design process. All you have to do is describe your applications interface in XML and write the appropriate event handlers. You dont have to waste time and money on widget implementations. QuiX comes with a variety of ready to use widgets, accelerating the development process.

Generally, every Porcupine application consists of three distinct layers. The first is the business layer consisting of the business objects which encapsulate the business logic.
The second layer binds the HTTP protocol with the first layers business objects. This layer is implemented using Python Server Pages or Servlets. If using XML-RPC, one common approach is to directly map an XML-RPC method to a business objects method.
The third layer, the presentation layer, usually consists of XML UI definitions and JavaScript event handlers.

The first two layers are executed server side and the third layer is executed on the client (browser).

libfirerpc is a library that provides an easy interface for C programs to make remote function queries via the XML RPC protocol.

It supports SSL/TLS, HTTP authentication, HTTP 1.1 persistent connections and pipelining. It also supports POST data compression via bzip2 and response compression via bzip2, gzip, deflate and compress.

XML-RPC is a C library for remote procerure call. It converts the procedure call into XML document, sends it to a remote server using HTTP, and gets back the response as XML.
This library provides a new and modular implementation of XML-RPC for C and C++.
XML-RPC For C and C++ is designed for Unix and is most tested on unix. As far as we know, it works on any reasonably standard unix.
There is also lots of code to make it work on Windows, but the fact is that it probably wont work out-of-the-box on your Windows system. Here is the Windows story.
To build a useful Xmlrpc-c client library, youll need to have at least one HTTP library. Xmlrpc-c knows how to use W3C Libwww (Version 5.3.2 or newer), Curl, and Wininet. The configurator gives you the option of building libraries that use any or all of these, and
defaults to every one you appear to have installed. If you dont appear to have any installed, the configurator causes the build to omit client facilities altogether.
Information about W3C Libwww, including how to get it are at .
For Curl, see .
Wininet comes with Windows, and isnt available for any other platform.
You also need an XML parser/builder library. An old version of Expat is included in the package and used by default, so theres no actual prerequisite here. But if you separately obtain Libxml2, you can configure the build to use that instead. Theres no really pressing reason to do that, though.
In the simplest case, the installation its just a conventional:
./configure
make
make install
Enhancements:
- Curl client XML transport: Use Curl multi-manager for synchronous RPCs to make them properly interruptible by signals. (Requires March 2007 update to libcurl to avoid delay of up to a second).
- Abyss: Fix per-HTTP-request memory leak.
- Abyss: Fix infinite loop reading headers when buffer contains data right up to the newline at the end of a header.
- Build: works on a system with no pselect(). (emulates with select()).
- Fix compilation failure in thread_fork.c when you configure with --disable-abyss-threads.

perlrpcgen is a Perl module that can generate Perl interfaces from ONC RPC interface definitions.

SYNOPSIS

perlrpcgen [--makefile] [--all] [--client] [--server] [--data] [--constants] [--module module] [--typemap typemap] [--fork] [--perl perl] [--cc cc] [--rpclibs rpclibs] rpcfile.x

perlrpcgen builds a set of Perl extensions and a server shell from an ONC RPC interface definition. For an interface Foo, perlrpcgen creates modules Foo::Client, Foo::Data, and Foo::Constants. Foo::Client contains routines for creating a Foo client and making remote procedure calls via the client. Foo::Data contains routines for creating and manipulating the data structures defined in the Foo interface. Foo::Constants contains functions to retrieve the constants defined in the Foo interface.

OPTIONS

The option parsing uses Getopt::Long, so you can abbreviate option names.

--makefile

Generates a top-level Makefile which will build all the pieces. Include all the other options you want so theyll be propagated to the Makefile.

--all

Implies --client, --server, --data, and --constants. This is usually what you want.

--client

Generates Foo::Client module.

--server

Generates Foo/server/foo_svc.

--data

Generates Foo::Data module.

--constants

Generates Foo::Constants module.

--module module

Sets the basename of the modules. If not given, the name defaults to the basename of the interface file.

--typemap typemap

Uses the given typemap during stub generation. This option can be specified many times. perlrpcgen generates a typemap for the data structures in the interface, but you also need the main Perl typemap.

--fork

Munges the server shell code so that it forks for each request. You probably dont want to do this (its better to prefork several processes when you start the server and let them fight over accept() calls).

--perl perl

Sets the Perl binary against which extensions should be built. Defaults to the Perl you used to install perlrpcgen.

--cc cc

Sets the C compiler to use. Defaults to the compiler used when building Perl.

--rpclibs rpclibs

Sets the RPC libraries to link against. Defaults to -lnsl -lrpcsvc.

Jabber::RPC is a Jabber-RPC Implementation.

SYNOPSIS

See documentation for Jabber::RPC::Server and Jabber::RPC::Client.

Jabber::RPC is a library that implements Jabber-RPC for Perl. The library consists of two modules, Jabber::RPC::Server and Jabber::RPC::Client. Please refer to the documentation for these two modules for more information.

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.