Free resources on call software for linux

RPyC stands for Remote Python Call, a pun over remote procedure call. It is completely transparent and symmetrical. It is inspired by the work of eyal lotem (pybuild.sf.net) on pyinvoke, and was made for two purposes:
Learning the lowlevel of the python language attempting to improve pyinvoke by making the entire protocol symmetrical. This means the client can make requests to the server, and the server can reply with requests of its own (the client is also a server on its own). This typically means using callback functions.
The RPyC package comes with a full demo, showing (or showing-off) many of its features. As i said, its completely transparent and symmetrical, so you can write code just as you would write in the case of normal python programs.
demo 1 -- a simple client demo
# import the client
from Rpyc.Client import RpycSocketClient
# `hostname` is the name of the host running an Rpyc server
# the port parameter is optional
c = RpycSocketClient("hostname")
# now we are connected and can start messing around with stuff on the server
for filename in c.modules.os.listdir("/tmp"):
print "found file", filename
Enhancements:
- This release adds DeliveringNamespace, LoginError (instead of tlslites internal errors), __version__, deliver (the counterpart of obtain, which can now deliver and obtain functions as well), and isproxy (to test whether an object is a proxy).
- It improves memory consumption with __slots__ and the isinstance/issubclass mechanism.

GRIA (Grid Resources for Industrial Applications) is Grid middleware that enables use of the Grid in a secure, interoperable and flexible manner.
Security
GRIA uses off-the-shelf Web Services technology and Public Key Infrastructure (PKI) security.
Trust
GRIA supports well established B2B processes & trust models.
Ease of use
GRIA is designed to support leading-edge and legacy application codes, and client-side applications can be easily written using the GRIA API.
Quality of Service
GRIA resource models allow service levels to be matched to clients needs.
Support
GRIA is supported through an open source community and on a commercial basis.
Enhancements:
- This release provides significant new features and usability enhancements to both the management packages and the client.
- The core infrastructure stack has been further aligned with key Web Service security and policy specifications.
- New services include a Membership Service, Registry Service, and an improved SLA service.

XML::DB::Resource is a Wrapper class for documents or document fragments.

SYNOPSIS

$resource = $collection->getResource($id);
$id = $resource->getId();
$xml = $resource->getContent();
$resource->setContent($xml);
$collection->storeResource($resource);
$parentColl = $resource->getParentCollection();

This is an abstract class implementing the Service interface Database from the XML:DB base specification. It should only be used indirectly, as superclass for a specific Resource type. The only current example is XMLResource.

TN3270RG is a TCP/IP TN3270 gateway that dynamically assigns resources to a connection from a pool of available addresses. Features include an easy to use web interface for management and a PostgreSQL database backend.
It is useful if you have a large number of machines connecting to a TN3270 host, but for whatever reason the host itself cannot assign resources from a pool. TN3270 will keep track of a pool of resources in a PostgreSQL database (should work with other databases as well) and dynamically allocate a resource to each connnection that goes through it.
Simply configure the daemon so it knows the address of the real TN3270 host, set the resource pool up using the web management software, and point your clients to the address of the gateway.
In the client configuration set your resource to what you have the replacement token set to (!_TN3270RG_RESOURCE_! by default) and when the daemon sees that resource go by, it will substitute the resource it has allocated for the connection and pass the rest of the data stream unaltered to the host.
TN3270 Resource Gateway project is designed to be fast and stable and should recover gracefully from most errors including unexpected disconnections and database errors. It is written in Perl and uses the POE framework.
Enhancements:
- This release uses Sys::Syslog (which is actively maintained and is included in the main Perl distribution).
- All Syslog calls have been updated to prevent a highly unlikely (but still possible) format string vulnerability.
- It cleanly exits from a SIGTERM with useful logging information.

Crypt::OpenSSL::CA::Resources is a bibliography of documentations and tools that I found helpful for implementing X509 PKIs in Perl over all these years.

This package performs the cryptographic operations necessary to issue X509 certificates and certificate revocation lists (CRLs). It is implemented as a Perl wrapper around the popular OpenSSL library. All certificate and CRL extensions supported by OpenSSL are available, and then some.

Shezhu Resource Sharing System project is an application for scheduling and booking shared resources such as rooms and equipment.
The client only needs a modern Web browser.
It has a user friendly point and click interface, visual filters for making block/repeat bookings, concurrent users and double booking prevention, allows local site customization, and supports configurable academic term/semester blocks.
Main features:
- Portable - client only needs a modern web browser
- Point and Click - almost no typing required
- Intuitive - simple, obvious, consistent and user friendly
- Innovative - visual filters for making block/repeat bookings
- Powerful - concurrent users and double booking prevention
- Configurable - local site customization supported
- Useful - built in support for configurable academic term, semester and session blocks
- Free!
Requirements
In order to run or build the Shezhu Resource Sharing System you need some third-party software available on your machine.
Client
The client needs a modern web browser and the best browsers for this application are Firefox, Mozilla (including the Netscape branded equivalent and Gecko derivatives such as Galeon) and Microsoft Internet Explorer. The newest versions of all these browsers will work best. This application also works with the Konqueror and Opera browsers but these have some issues which may affect functionality. All browsers need JavaScript enabled. Any of these browsers may not work properly (or at all) depending on the operating system they are running under. Text based browsers (such as Lynx) are not supported.
For a comprehensive list of supported client browsers and operating systems refer to this browser compatibility chart from the most recent release of the application.
Server
The server needs recent versions of the Apache web server and the MySQL database server.
The server has only been tested on Redhat9 and FedoraCore3 Linux/i386 platforms although there is no specific reason why it should not work on other Linux platforms and distributions.
Development
Rebuilding this application from source requires a standard Unix development environment with the sh, make, cc, cpp, sed and awk utilities. Also required are RCS, Perl (5.6+) and the ImageMagick program. Also required is RPM to build a distribution. All these programs would probably come as standard in Linux distributions, other platforms may not have all of them by default.
Enhancements:
- This release adds support for Apache2 and multi-site installations, internal restructuring, a better installation tree, and improved access control management.

Voicent is a Perl interface for making telephone calls using Voicent Gateway.

You can use this interface module to make telephone calls from your perl program, provided that the Voicent Gateway is installed and can be accessed through HTTP. There is a FREE version of Voicent Gateway program downloadable from:

http://www.voicent.com/download

SYNOPSIS

use Voicent;

call_text < phone number > < text message > < selfdelete >
call_audio < phone number > < audio file > < selfdelete >
call_status < call reqId >
call_remove < call reqId >
call_till_confirm < vcast exe > < call list voc > < confirm code > < wavefile >

Example

call_text(123-4567, Hello, how are you doing, 1);

Make a call to phone number 123-4567 and say Hello, how are you doing. Since the selfdelete bit is set, the call request record in the gateway will be removed automatically after the call.

$reqId = call_text(123-4567, Hello, how are you doing, 0);

Make a call to phone number 123-4567 and say Hello, how are you doing. Since the selfdelete bit is not set, the call request record in the gateway will not be removed after the call. You can then use call_status to get the call status, or use call_remove to remove the call record.