Free metaframe presentation server client for 32 bit windows software for linux

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.

Pluto Request Action Library allows you to create a client/server application, where client sends requests, server replies with responses and optional actions. Very object oriented, and takes only minutes to get going. Same library used for both server & client side.

How does it work?

The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.

The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.

In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.

On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.

Net::Nessus::Client is a Nessus client module.

SYNOPSIS

# Connect to the Nessus Server
require Net::Nessus::Client;
my $client = Net::Nessus::Client->new(host => localhost,
port => 1241,
user => joe,
password => my_password);

The Nessus program is a Client/Server application offering a framework for lots of security related scanners, so-called plugins. The idea is not to create a separate scanner for any possible security hole, but to reimplement only the most important parts and let the Nessus Server (nessusd) do the most part of the work.
Clients are typically available as GUI applications, for example based on the GTK (nessus), Java or Win32 applications. This module is another Nessus client written in Perl, but without GUI.

You start using the module by opening a connection to a Nessus Server: This will create a Nessus client object for you. This object offers methods that you can later use, for example retrieving the list of available plugins, start a scan, set preferences and so on.

LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. It takes care with the number of clients using the connection and decides upon this number whether the connection should be up or down.
The clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)

DTLS Client/Server Example contains a simple DTLS client and DTLS server to show how to send UDP data over an encrypted channel using OpenSSL DTLSv1 support.

LIST OF FILES:

Directory: common - Contains callback functions and error reporting functions common to client and server

sslmgr.h
sslmgr.c

Directory: dtls_server

dtls_server.c - DTLS server part

Directory: dtls_client

dtls_client.c - DTLS client part

FUSE::Client is a Perl-FUSE client.

SYNOPSIS

use FUSE::Client;
$c = FUSE::Client->new({
Port=>35008,
Quiet=>1,
});

$c->connect();
$c->send("COMMAND","parameter");
$c->disconnect();

The FUSE::Client module will create a TCP FUSE client to test sending messages to a FUSE server.

The external interface to FUSE::Client is:

$c = FUSE::Client->new( [%options] );

The object constructor takes the following arguments in the options hash:

Quiet = 0|1

Whether to be quiet. Default is to report all events to STDOUT (not Quiet).

Port = n

The port for the client to connect to. Default is 1024.

$c->connect();

This method connects the client to the server.

$c->disconnect();

This method disconnects the client from the server.

$c->send( $command, $parameter );

Send a FUSE formatted command message to the server, with the specified parameter.

iConnect Portal Server is a data presentation and delivery system for building enteprise portals over the iConnect Web Application Server.
Users of the platform have a customized single point of access to the companys information system and resources.
Main features:
- Grid / slots / blocks logic
- Modular structure
- Encapsulation of pages, blocks and classes inside modules
- Separation between view and model
- PHP as template engine
- Localized templates
- Grid themes
- Sessions