perlmsgque Tutorial

INDEX

INTRODUCTION
BUILD
SERVER
CLIENT
FILTER

INTRODUCTION

perlmsgque is the perl language binding of the libmsgque library.
The library was designed to simplify the client/server development using the following design rules:

1. programming language independent
2. operating system independent
3. processor hardware independent

The perl language binding provide the following basic components:

• abstract class of the perlmsgque object: MqS
• interface: IServerSetup and or IServerCleanup to add server functionality
• interface: IFilterFTR and or IFilterEOF to add filter functionality
• interface: IFactory to create a new application instance
• interface: IBgError to act on asyncrone errors
• adding and removing services

BUILD

The build is different between UNIX and WINDOWS. On UNIX the automake (info automake) build environment is used and on WINDOWS the VisualExpress tools from Microsoft are used. The automake build on WINDOWS is possible but not supported.

UNIX

The example from the tutorial is using the automake build-environment from the perlmsgque tool. An example automake configuration file is available in: example/perl/Makefile.am

no build necessary

WINDOWS

The VisualExpress build environment is located in the directory win.

SERVER

A perlmsgque server requires the following setup:

1. file: example/perl/MyServer.pl
2. an instance of the abstract class MqS
3. the interface IServerSetup and or IServerCleanup
4. the interface IFactory to create a new application instance

The minimal server looks like:

use strict;
use Net::PerlMsgque;

package MyServer;
use base qw(Net::PerlMsgque::MqS);

  sub HLWO {
    my $ctx = shift;
    $ctx->SendSTART();
    $ctx->SendC("Hello World");
    $ctx->SendRETURN();
  }

  sub ServerSetup {
    my $ctx = shift;
    $ctx->ServiceCreate("HLWO",\&HLWO)
  }

  sub new {
    my $class = shift;
    my $ctx = $class->SUPER::new(@_);
    $ctx->ConfigSetName("MyServer");
    $ctx->ConfigSetServerSetup(\&ServerSetup);
    $ctx->ConfigSetFactory(sub {new MyServer()});
    return $ctx;
  }

package main;

  our $srv = new MyServer();
  eval {
    $srv->LinkCreate(@ARGV);
    $srv->ProcessEvent({wait => "FOREVER"});
  };
  if ($@) {
    $srv->ErrorSet($@);
  }
  $srv->Exit();

The server is started as network visible TCP server listen on PORT 2345 using a THREAD for every new connection request:

> perl MyServer.pl --tcp --port 2345 --thread

If you are using UNIX and if you want to setup a high-performance local server then use the build-in UDS (Unix-Domain-Sockets) capability to listen on the FILE /path/to/any/file.uds instead on a network port:

> perl MyServer.pl --uds --file /path/to/any/file.uds --thread

Three things are important:

1. the send style of functions
2. the $ctx->ServiceCreate(token, callback) function
3. a connected context of type MqS

Sending data is done using a minimum of 2 steps:

1. First: start a data package with $ctx->SendSTART()
2. Last: submit the a data package to the link target using one of:
   • $ctx->SendEND(token)
   • $ctx->SendEND_AND_WAIT(token, timeout=seconds)
   • $ctx->SendEND_AND_CALLBACK(token, callback)
   • $ctx->SendRETURN()

The first three SendEND... functions are used to call a remote service and the last one is used to answer an incoming service call. In-between $ctx->SendSTART() and $ctx->SendEND(token) ... other SEND DATA style commands are available to fill the data package with data.

Services are created with the $ctx->ServiceCreate(token, callback) function. The first parameter is a 4 byte Token as public name. 4 byte is required because this string is mapped to a 4 byte integer for speed reason. The second parameter is an object providing the SERVICE CALLBACK interface.

The SERVICE CALLBACK function has one parameter of type MqS. This parameter refer to the original object (in our case MyServer). If the service object (in our case MyFirstService) is a subclass of the original MqS object class, the both statements SendSTART() and ctx.sendSTART() are identical.

CLIENT

A perlmsgque client requires the following setup:

1. an instance of the abstract class MqS

The minimal client looks like:

use strict;
use Net::PerlMsgque;

package main;

  our $ctx = new Net::PerlMsgque::MqS();
  eval {
    $ctx->ConfigSetName("MyClient");
    $ctx->LinkCreate(@ARGV);
    $ctx->SendSTART();
    $ctx->SendEND_AND_WAIT("HLWO");
    print $ctx->ReadC() . "\n";
  };
  if ($@) {
    $ctx->ErrorSet($@);
  }
  $ctx->Exit();

To call a network visible TCP server listen on PORT 2345 use:

> perl MyClient.pl --tcp --port 2345
> Hello World

To call a network visible UDP server listen on FILE /path/to/any/file.uds use:

> perl MyClient.pl --udp --file /path/to/any/file.uds
> Hello World

To call a local server started by the client using PIPE communication use:

> perl MyClient.pl @ perl MyServer.pl
> Hello World

FILTER

A filter has to implement the IFilterFTR or the IFilterEOF interface which requires the following functions:

• IFilterFTR, a service function to act on filter data rows. Every filter input data is a list of filter data rows and every row is a list of filter data columns. Every row is send from one filter-command to the following filter-command as FTR service request
• IFilterEOF, a service function to act on End-Of-Filter data. This service is called after the whole filter data was send. Sometimes the filter data can not be served as filter data rows (example: sorting of the input rows need to read all rows before the data can be send to the next filter command) and the EOF function is used to continue send filter data rows

The minimal filter looks like:

• filter example