# Kitty - your client code. #!/usr/bin/perl -w use warnings; use strict; use IO::Socket::INET; my $client; my $server; my $remote_port = 8100; my $remote_host = "localhost"; my $line; $server = IO::Socket::INET->new( PeerAddr => $remote_host, PeerPort => $remote_port, Proto => "tcp", Type => SOCK_STREAM ) or die "Couldn't connect +to $remote_host: $!\n"; print $line = <$server>; close $server; # Server code. #!/usr/bin/perl -w use strict; use IO::Socket::INET; my $server_port = 8100; my $client; my $line; my $server = IO::Socket::INET->new( LocalPort => $server_port, Type => SOCK_STREAM, Reuse => 1, Listen => 10 ) or die "Could not create a tcp server on port $server_port : $!\n"; while( $client = $server->accept() ) { open( FH, "<data.txt" ) or die "Couldn't open 'data.txt' : $!\n"; rand( $. ) < 1 and ( $line = $_ ) while <FH>; close FH; print $client "$line\n"; }
Testing... testing....

After outlining my dilemma in this node , the subsequent research lead me to a product that is being touted as a "MS Exchange Killer". The general sway of the project is to provide MS outlook clients with the necessary 'services' to leverage MOST of the groupware functionality that Exchange gives. Cost, scalability and performance are the areas that are its hilights.

Great toaster, so WTF is this all about then... OK - check out the information on Insight Server , Insight Connector and Insight LDAP Client, all at In simple terms, the two Middleware plugins for outlook (Connector and LDAP Client), are installed and configured to point to Insight Server.

The Server

The server is kind of complicated, although it was one of the simplest installation dances I have ever performed. There are three main components.

The Plugins

Insight connector is easy to add as a service, with fairly common and obvious settings, hostname of server, username, password , Use TLS. The Connector places four buttons in the Outlook toolbar.