libmsgque is a connectivity toolkit with the main goal to 
serve as bridge between an '''API''' and a '''programming toolkit''' 

'''API'''

near all application toolkits offering an ''API'' to give
the user a chance to integrate the application toolkit into the local
environment. example:
   * Databases (by Oracle, Sybase, Microsoft, IBM, ...)
   * Application Frameworks (by SAP, Oracle, Peoplesoft, Remedy, ...)
   * System Management Tools (by IBM, HP, Free/Share/Open - Ware, ...)


'''programming toolkit'''

a programming toolkit serve as an interface between the human and the
computer. The human create input, knows as source-code, to instruct
the computer to do complex work. example:
   * tcl, perl phyton, ruby (known as scripting languages)
   * java, C# (known as application framework languages)
   * C, C++, Fortran (known as system programming languages)


'''libmsgque'''

libmsgque acts as a bridge between a programming toolkit and an API:

  >>>>>>>>>>>>>>> REQUEST >>>>>>>>>>>>>>

  |     | ---> |           | ---> |     |
  | Tcl |      | libmsgque |      | API |
  |     | <--- |           | <--- |     |

  <<<<<<<<<<<<<<<< ANSWER <<<<<<<<<<<<<<

A REQUEST will be submitted with libmsgque from the ''programming toolkit''
to the ''API'' and the ANSWER will be send back. 
the advantage of libmsgque is:
   1. the ''programming toolkit'' and the ''API'' were separated into '''independent''' processes
   2. the interface between the ''API'' and ''libmsgque'' is independent from the interface between the ''programming toolkit'' and ''libmsgque''
   3. the interface between the ''programming toolkit'' and ''libmsgque'' is '''only''' written with the ''programming toolkit'' '''language''' (example: Tcl, '''no''' C knowledge required)


'''link to Tcl'''

   * ''TclMessageQueue'' is an Tcl extension using libmsgque
   * ''TclMessageQueue'' is included into [TclBase]
   * [Andreas Otto] wrote [libmsgque], TclMessageQueue and [TclBase]