MQ_C_API

theLink - a API to link multiple package-items together to act as one application … More...

Collaboration diagram for MQ_C_API:

Topics
	MqMsgque_C_API
	MqMsgque PACKAGE - the package is the toplevel structure of the pymqmsgque …
	MqRuntimeC_C_API
	MqRuntimeS - the class known as rt or runtime is main pymqmsgque application environment …
	MqEnvC_C_API
	MqEnvS - the class known as env or environment is used to store the protected environment in an service-call …
	MqContextC_C_API
	MqContextC - the class known as ctx or context is the application-handle of the application-server and also the main data-handle …
	MqDumpC_C_API
	MqDumpC - the class known as dmp or dump is used to export a pymqmsgque data package as binary …
	MqFactoryC_C_API
	MqFactoryC - the class known as fct or factory is used to provide an interface to create one or more new MqContextC …
	MqErrorC_C_API
	MqErrorS - the class known as err or error is the extension of the kernel-error MkErrorS …

Detailed Description

theLink - a API to link multiple package-items together to act as one application …

PHILOSOPHY

The theLink project is an infrastructure that allows multiple package-items to be linked together to act as one application.
To link, you need to distribute the work from one package-item to another package-item and wait for an answer or not.

Philosophy

Write Once → Run Everywhere

The package-item can be a thread, a separate local process that is started by fork or spawn, or even a network of multiple services on multiple hosts.

The package-item can be written in any language that is supported by the Programming-Language-Micro-Kernel (PLMK) support.
It even supports running multiple programming languages in a single piece of software.
Supported Languages are: (C,C++,C#,VB.NET,Java,Python,Ruby,Perl,PHP,Tcl or GO)

Strategy

It takes 4 years to write a programming-language, but it only takes 4 weeks to insert a micro-kernel.

The package-item is connected to one another via a pipe or a socket and is based on packages which are sent from one package-item to another package-item and back.

Conclusion

theLink is used to manage a network of multiple package-items using an API that is available in all major programming-languages.

PROGRAMMING

theLink is responsible for:

• establishing and managing the package-items, local or remote
• establishing and managing the connections between package-items
• establishing and managing the routing between package-items
• sending and receiving the package data, calling up a service
• reading and writing data from or into a data-package
• setup and maintain event-handling and scheduling
• interception, distribution and processing of error messages

The LibMsgque library is separted into three programming-layers:

1. The foundation-layer, used by theLink library programmer
2. The kernel-layer, used by the Programming-Language-Micro-Kernel programmer
3. The implementation-layer, used by the target-language programmer

foundation-layer

The foundation-layer implement the libmqmsgque library and is also responsible for the quality-target of the entire project.

• establishing and managing the package-items
• establishing and managing the connections
• memory-management and garbage-collection
• error-handling
• logging and debugging
• written in plain C

kernel-layer

The kernel-layer implement the Programming-Language-Micro-Kernel and is also responsible to generate and maintain the target-language-API source-code.

• implementation of the managed-object technology
• implementation of the token-stream-compiler technology
• written in plain C, TCL and the target-language-API

implementation-layer

The implementation-layer is the API used by the target-language-programmer.

• written in plain Target-Programming-Language (TPL)

Target

!! This documentation describe the implementation-layer and target the Python programmer. !!