PVM (Parallel Virtual Machine) is a portable message-passing programming
system, designed to link separate host machines to form a virtual machine
which is a single, manageable computing resource.
The virtual machine can be composed of hosts of different architectures,
located in physically remote locations. PVM applications can be composed
of any number of separate processes, or components, written in a mixture
of C, C++, and Fortran. The system is portable to a wide variety of
architectures, including workstations, multiprocessors, supercomputers,
and PCs.
POEx::Role::TCPServer bundles up the lower level
SocketFactory/ReadWrite combination of wheels into a simple
Moose::Role. It builds upon other POEx modules such as
POEx::Role::SessionInstantiation and POEx::Types.
The events for SocketFactory for and for each ReadWrite instantiated
are methods that can be advised in any way deemed fit. Advising these
methods is actually encouraged and can simplify code for the consumer.
The only method that must be provided by the consuming class is
handle_inbound_data.
Paraller::Pvm is a perl interface to the Parallel Virtual Machine (PVM)
Message Passing System.
The PVM message passing system enables a programmer to configure a group
of (possibly heterogenous) computers connected by a network into a
parallel virtual machine.
Using PVM, applications can be developed which spawns parallel processes
onto nodes in the virtual machine to perform specific tasks. These
parallel tasks can also periodically exchange information using a set of
message passing functions developed for the system.
PVM applications have mostly been developed in the scientific and
engineering fields. However applications for real-time and
client/server systems can also be developed. PVM simply provides a
convenient way for managing parallel tasks and communications without
need for rexec or socket level programming.
pRPC-modules (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 the RPC::pServer(3) and RPC::pClient(3) manpages for detailed
information.
-Vanilla
vanilla@FreeBSD.ORG
This module acts as a base class for applications which implement a
RESTful interface. When an HTTP request is received some dispatching logic
in REST::Application is invoked, calling different handlers based on what
the kind of HTTP request it was (i.e. GET, PUT, etc) and what resource it
was trying to access. This module won't ensure that your API is RESTful
but hopefully it will aid in developing a REST API.
REST::Google -
This module provides OO interface to Google REST (aka AJAX) API.
Currently support for Search, Feeds and Translate services.
This module enables to connect the other process with the S-expression
protocol, like the Swank protocol of the SLIME.
The primary objective is for users to make some Emacs extensions with
the Perl and CPAN.
perl5 module to communicate with socks v4 and v5 servers
This module implements remote procedure call. I've tried to keep things simple.
So this module should be:
- quite simple to use (thanks to autoload mechanisms)
- lightweight
It sure is not:
- DCE
- CORBA
- bulletproof
- securityproof
- foolproof
But it works. (Although I'm opened to suggestion regarding the "un-proof" areas)
The RPC::XML package is an implementation of XML-RPC. The module
provides classes for sample client and server implementations, a
server designed as an Apache location-handler, and a suite of
data-manipulation classes that are used by them.