Free client application software for linux

SOPE Application Server is an extensive set of frameworks (16 frameworks, ~1500 classes) which form a complete Web application server environment.
Besides the Apple WebObjects compatible appserver extended with Zope concepts, it contains a large set of reusable classes: XML processing (SAX2, DOM, XML-RPC), MIME/IMAP4 processing, LDAP connectivity, RDBMS connectivity, and iCalendar parsing.
The individual frameworks of the package can be used standalone (for example in Cocoa applications) and do not require the application server itself.
For MacOSX developers, the package includes SOPE:X, which contains special Xcode and Cocoa support for SOPE.
Enhancements:
- This release fixes a set of minor bugs.
- It improves the vCard parser, the IMAP4 client library, the MySQL adaptor, and BSD packaging.

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.

MiniUPnP Client and Daemon is an UPnP IGD client lightweight library and UPnP IGD daemon.
The UPnP protocol is supported by most home adsl/cable routers and Windows 2K/XP. The aim of the MiniUpnp project is to bring a free software solution to support the "Internet Gateway Device" part of the protocol.
The Linux SDK for UPnP devices (libupnp) seems too heavy for me. I want the simplest library possible, with the smallest footprint and no dependencies to other libraries such as XML parsers or HTTP implementations. All the code is pure ANSI C.
Compiled on a x86 PC, the miniupnp client library have less than 15KB code size. For instance, the upnpc sample program is around 20KB.
The project is divided in two main parts : the client library, enabling applications to access the services provided by an UPnP "Internet Gateway Device" present on the network, and the miniupnpd daemon, providing these services to your network from a linux or bsd box being the gateway. At the moment the miniupnpd is developped on OpenBSD 3.0+ with pf. You can see some of the work I have done to integrate with pf on this page.
As pf is also available under FreeBSD, guys at the pfSense project have ported miniupnpd to this system.
For some reasons, it may be not the good solution for you to use the code from the MiniUPnP project directly.
As the code is small and simple to understand, it is a good base to take inspiration for your own UPnP implementation. The KTorrent team UPnP plugin in C++ is a good example.
If you are wondering which home router is working with the miniupnp client, you can find the answer here. In fact, you are more likely to help me fill the list by sending me an email.
Usefulness of the miniUPnP client library
The usage of the miniUPnP client library is useful whenever an application needs to listen for incoming connections.
Examples : P2P applications, FTP clients for active mode, IRC (for DCC) or IM applications, network games, any server.
The typical usage of UPnP capabilities of a router is a file tranfert using MSN messenger. The MSN Messenger software uses the UPnP API of Windows XP to open port for incoming connection. To mimic the MS software, it is a good idea to use UPnP as well.
Enhancements:
- This release adds changes to accommodate the Linux 2.6.22 kernel.

reacTIVision is an open source, cross-platform computer vision framework for the fast and robust tracking of fiducial markers in a real-time video stream. reacTIVision project was mainly designed for the rapid development of table-based tangible user interfaces.

Its tracking core is using Ross Bencinas fidtrack library which is basically a newer high-performance implementation of Enrico Costanzas original d-touch concept. This framework was developed by Martin Kaltenbrunner et.al. at the Music Technology Group, IUA, UPF in Barcelona, Spain as part of the reacTable* project, a novel electro-acoustic musical instrument with a tangible user interface.

reacTIVision is a standalone application, which sends OpenSound Control messages via a UDP network socket to any connected client application. It implements the TUIO protocol, which was specially designed for transmitting the state of tangible objects on a table surface. This framework includes a set of free example client projects for various programming languages, which serve as a base for the easy development of tangible-user interface applications.

The reacTIVision application compiles and runs under the follwing operating systems: Win32, MacOS X and Linux. Under Win32 it suports any camera with a proper WDM driver, such as USB, USB2, FireWire and DV cameras. Equally under MacOS X any such camera supported by QuickTime will work in reacTIVision. Under Linux, FireWire cameras are best supported, as well as a few Video4Linux USB cameras.

NEW: Support the reacTIVision project and buy T-Shirts, posters and other merchandise featuring the reacTIVision fiducial symbols in our web-shop! All designs on these products can be recognized and tracked by the actual reacTIVision software.

Application Handling

Before starting the reacTIVision application make sure you have a supported camera connected to your system. The application can and will not work at all without a camera. Under Win32 and MacOS X the application will ask to select and configure the camera upon startup. Under Linux the camera will be selected automatically. Once configured the application will show a video window with the current camera image in black&white.

Pressing T will show the binary tresholded image, pressing the N key will turn the display off, which reduces its CPU usage significantly!

Pressing the S key will return to the original source image. For convenience and debugging porposes hitting the R key saves a raw image frame, while hitting the B key will save an image in the BMP format.

The P pauses the image analysis completely, hitting ESC will quit the application. The F key toggles the diplay of FPS info in the titlebar. In order to produce some more verbose debugging output, hitting the V key will print the currently recognized symbols to the console.

Command Line Options

The reacTIVision application per default sends the TUIO messages to port 3333 on localhost (127.0.0.1)

In order to change these parameters you can invoke the application with the -h [ip-address] and -p [port-no] options.

reacTIVision needs a so called "tree file" in order to function properly. The default "all.trees" is included and loaded automatically. If you want to use you own tree file you can invoke the application with the -t [tree-file] option.

Optionally if you dont want to analyze the complete image - for example in a square or round table setup - the application can mask a part of the video image with a black region, which speeds up the segmentation algorithm. In order to apply this mask You can invoke the application with the -m [square,circle] option.

Applying the -h or -help option will print a usage message to the console.

Calibration and Distortion

Some tables, such as the reacTable are using a convex mirror in order to increase the area visible to the camera at a minimal distance. This mirror as well as a fish-eye lens unfortunately distort the image. reactIVision includes a correction algorithm, which corrects this distortion with the help of a so called "grid file". These grid files can be generated during a prior calibration process.

To calibrate reacTIVision invoke the application with the option: reacTIVision -c 9 -g [grid_file]

In order to use the this calibration invoke the application with: reacTIVision -g [grid_file]

SILC (Secure Internet Live Conferencing) is a protocol which provides secure conferencing services in the Internet. It can be used to send any kind of messages, in addition to normal text messages.
This includes multimedia messages like images, video, and audio stream.
All messages in the SILC network are encrypted and authenticated, and messages can also be digitally signed. SILC protocol supports AES, SHA-1, PKCS#1, PKCS#3, X.509, OpenPGP, and is being developed in the IETF.
The software is delivered as SILC Client for end users, SILC Server for system administrators, and SILC Toolkit for application developers.
Enhancements:
- This version fixes several crash bugs and other minor bugs.

Oracle client is a simplistic Perl-based Oracle client that tries to mimic some of the functionality of PostgreSQL and MySQLs text-based SQL clients.

It is relatively simplistic, but much more useful than dbishell or sqlplus.

The project supports readline, history, desc, and various shorthand commands like d, , c, etc.

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