Free automated support for compound rpc calls 0.2 software for linux

Zimbra Collaboration Suite project is a client/server technology for enterprise messaging and collaboration.
Zimbra delivers innovation for both the administrator and the end-user as well as compatibility with existing infrastructure and applications (both open source and proprietary).
The Zimbra Collaboration Suite provides support for email, contacts, and group calendaring, and consists of a server and client.
Main features:
Administrator Benefits
- Online move, backup and recovery of individual or a group of mailboxes
- Compatibility with Active Directory and existing LDAP directories
- Native hierarchical storage management and clustering
- Web services integration with existing enterprise applications
- Integrated anti-spam and anti-virus
End-User Benefits
- Browser based client with search, shared calendar and mail that is integrated with contacts and calendar
- Support for Outlook: calendar, mail, contacts and offline mode
- Support for mobile devices: Blackberry, Treo and etc
- Support of Windows, Apple and Linux computer.
Whats New in 5.0.0 Beta 1 Development Release:
- This is the first release in the 5.0.0 release cycle.
- New features include IM, Tasks, Standard Client autocompletion, and keyboard navigation.
- Updates have been made to migration wizards and apple/outlook connectors.
Whats New in 4.5.6 Stable Release:
- Support for an automated MySQL database corruption check that will send a notification to the admin.
- Spam training has been enhanced by allowing programmatic scanning of folders without requiring a password.
- Admins can get backup and restore complete notifications sent via email.
- .Doc and .pdf files open correctly in Zimbra Web Client.
- iSync will not duplicate the calendar, and iSync Connector works correctly with Mac OS X 10.4.10.
- Servers automatically start after a ZCS upgrade.
- Web-based cross-mailbox discovery is available for the optional Zimbra Archiving and Discovery module.

Automated support for compound RPC calls is a project which augments RPCGEN to support NFSv4-style compound procedures.

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.

Jabber::RPC::HTTPgate is an HTTP gateway for Jabber-RPC / XML-RPC.

SYNOPSIS

use Jabber::RPC::HTTPgate;

my $gw = new Jabber::RPC::HTTPgate(
server => myserver.org:5701,
identauth => jrpchttp.localhost:secret,
httpcomp => http,
);

$gw->start;

Jabber::RPC::HTTPgate is an experimental gateway that provides a conduit service between traditional (HTTP-transported) XML-RPC encoded requests/responses and Jabber-RPC (XML-RPC encoded requests/responses transported over Jabber).

The idea is that you can start a gateway, that connects as a component to the backbone of a Jabber server, and it proxies Jabber-RPC to HTTP-based XML-RPC endpoints, and vice versa. That means that your Jabber-RPC client can not only make XML-RPC encoded calls to a Jabber-RPC endpoint but also to a traditional HTTP-based XML-RPC endpoint. And it also means that your traditional HTTP-based XML-RPC client can make XML-RPC encoded calls to a Jabber-RPC endpoint.

Jabber -> HTTP

When you create and start up a gateway, it listens for Jabber-RPC calls, just like a normal Jabber-RPC responder. On receipt of such a call, the gateway creates an HTTP request and sends this request on to the HTTP-based XML-RPC endpoint. The response received back from this HTTP call is relayed back to the original Jabber-RPC requester.
While a Jabber-RPC endpoint address is a Jabber ID (JID), an traditional XML-RPC endpoint address is a URL. So all the Jabber-RPC client needs to do is specify the URL in the resource part of the gateways endpoint JID.

HTTP -> Jabber

As well as listening for Jabber-RPC calls, a gateway will also service incoming HTTP requests that can be made to the HTTP component that this gateway uses. The HTTP component (called simply http) can be downloaded from the normal Jabber software repository.

On receipt of an HTTP request (passed to it by the HTTP component), the gateway creates a Jabber-RPC request containing the XML-RPC encoded payload, and sends it on to the Jabber-RPC responder endpoint. This endpoint is identified (via a JID) by the path part of the URL used in the call by the traditional client.

NetCDF is a format developed at Unidata that was inspired by the CDF format from NASA.
NetCDF stands for "Network Common Data Form" and is a self-describing data format, commonly used in scientific and engineering applications.
Main features:
- All features of netCDF 3.6
- Large file support (> 2 GB data files)
- Use of HDF5 for storage
- Backward file-format compatibility
- Backward API compatibility
- Parallel I/O
- Multiple unlimited dimensions
- Additional Data Types
- Hierarchical Grouping of Data
- Bit packing
- Compression and other filters
- Revised documentation
- Examples
- Distribution with both netCDF and HDF5 packages
- (Unicode/ASCII) String data type
- Anonymous dimensions
- Support for compound data types, including nested compound types
- User-defined data type
- Upgrades to ncgen/ncdump/CDL to reflect new features
- NcML support for ncgen/ncdump
- F90 interface
- C++ interface
- Demonstrable performance gains in modeling contexts on advanced architectures
- HDF5 file driver support
Whats New in 4.0 Alpha 11 Development Release:
- Enum type added.
- NetCDF-4 verified support of common data model.
- ncdump support new features and NcML.
- No netCDF-4 artifacts in file.
- Uses HDF5 creation order information.
- NetCDF-4 documentation complete.
Whats New in 3.6.2 Stable Release:
- Support for shared libraries was added.
- Major documentation additions were done.
- Speedups were made on little-endian machines.
- Minor bugs were fixed.

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.

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.

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.

JavaDesktopEngines aim is to produce a piece of software that is at the same time:
Shared virtual machine
It allows to launch different java programs inside the same VM. The VM will always be alive, so no more startup overhead and less memory used.
It uses our JDSVM(Java Desktop Shared Virtual Machine), which in turn is based on Javagroups great Echidna Project
Xml Rpc local server
This way it is possible for programs, even written in languages different from java, to access "services" exposed by the engine.
Plugin host
It has been built with a pluggable architecture in mind, so that it is possible to develop new "services" for the engine.
Linux/Windows service (next release)
It is run as a service, so that its "services" will always be available for other programs.
For those of us who make heavy use of java tools its always been quite frustrating to have to open lots of resource eager VMs just to launch very useful but simple programs. Moreover, VM starting for simple utilities is a real waste of time.
Weve all appreciated the difference when launching a compilation from inside an IDE. In this case javac is launched as a process inside an already active VM, and the difference is evident.
JDE in the beginning was born to try to address these problems. Having an always active VM where it is possible to launch processes in, means faster process start and less resources used. A lot of time is saved by from not loading again and again the VM.
Theres nothing new in this. Some very good related projects are alive and kicking on the net, some of them focusing on a complete Java desktop enviroment, some on just a shared VM. JDE positions itself a bit differently, as it can be seen as a java engine exposing pluggable services (shared VM being just one of these).
There are several approaches to implementing a shared VM, all of them with pros and cons. Weve chosen to use the great code from the Echidna Project for now.
The entrypoint of JDE is an XML-RPC server accepting calls for services. Everything needed from JDE can be obtained by making a call to it.
The main service exposed by JDE is obviously the java process launching one. By making a call, it is possible to launch a java process insisde the VM. Having an XML-RPC server allows us to use any language with xmlrpc capabilities to launch java programs. The package includes a simple python script, that can be easily used as launcher (see our simple tutorial for details).
Included is also a "Manager", a simple swing application with active process listing and process launching capabilities.
Hopefully, this one will evolve as far as there will be more services in JDE to be the reference manager for the engine.
Included plugins:
1) Java process Launcher. The one this project was started for. You can launch java processes inside the living VM.
2) Scripting engine. Via a simple xmlrpc call you can launch a script on the engine and get back results. The nice thing, as usual, is that being xmlrpc based, you can use it as a service called by anything written in any language. Currently supported scripting language is BeanShell. More will be available soon via BSF.
3) Fast editor Based on jEdit Syntax Package 2.2.1, a simple, fast and useful editor with only some of the nice features jEdit has got us used to.
Enhancements:
- This release should be a bit more robust when killing processes that make use of System.exit(0) without "dispose()".
- An icon for the GUI manager has been added, as well as a bat file for Windows systems.