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

Terminal Server Client (tsclient) is a frontend for rdesktop and other remote desktop tools.
Main features:
- GTK+-2 frontend for rdesktop and other remote desktop tools
- GNOME panel applet to quickly launch saved profiles
- reads and writes profiles in the Microsoft format (.rdp), maintaining compatability with the Microsoft client
- similar look and functionality to the Microsoft client
- written in C using GTK and GNOME
- features a profile launcher which launches saved profiles
- Translated to 20+ languages.
- support for rdesktop 1.3
- support for VNC clients (*vncviewer)
- supported vnc options are -fullscreen, -geometry, -depth and -viewonly (set by checking "no motion events"). for a vncpasswd file, put the full path to the file in the username field.
- support for X via Xnest

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

YateClient is a next-generation telephony engine.
While currently focused on Voice over Internet Protocol (VoIP) and PSTN, its power lies in its ability to be easily extended.
Voice, video, data, and instant messaging can all be unified under Yates flexible routing engine, maximizing communications efficiency and minimizing infrastructure costs for businesses.
Yate can be used as a:
- VoIP server
- VoIP client
- VoIP to PSTN gateway
- PC2Phone and Phone2PC gateway
- H.323 gatekeeper
- H.323 multiple endpoint server
- H.323SIP Proxy
- SIP session border controller
- SIP router
- SIP registration server
- IAX server and/or client
- IP Telephony server and/or client
- Call center server
- IVR engine
- Prepaid and/or postpaid cards system

Messa is an instant messager client and server. The client has a curses interface and works on the console.

Messa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.

pDonkeyS is Perl implementation of an eDonkey server. The main goal of the server is to provide framework for further eDonkey protocol exploration, but it could be useful in testing of client software, since the server can be configured to output very detailed debugging info about eDonkey traffic.

This server was made to provide framework for further eDonkey protocol exploration, but it could be usefull in testing of client software, since the server can be configured to output very detailed debug info about eDonkey traffic.

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.

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.

Akeni Instant Messaging - Pro is a client/server instant messaging platform that allows companies to host their own secured private IM system. The client has an user interface similar to AIM, ICQ, or MSN Messenger. It supports all the standard IM features such as chat, group conference, presence management, file transfer, offline messages and emergency alert/notification. Extra features include contact management and optional tabbed chat sessions.

The server has administration tools like managing user accounts, client-side logging capabilities and peer-to-peer file transfers. Akeni Pro Messenger can be setup on a private network without connecting to the internet and can easily be setup for use inside and outside the company firewall.