https://sourceforge.net/p/umtsa/home/Home/Recent changes to HomeenFri, 17 Jun 2011 23:07:39 -0000https://sourceforge.net/p/umtsa/home/Home/<pre>--- v1 +++ v2 @@ -1,5 +1,12 @@ -Welcome to your wiki! - -This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage]. - -The wiki uses [Markdown](/p/umtsa/home/markdown_syntax/) syntax. +UNIVERSAL MULTI-THREADED SERVER +================================================================================ + +The Universal Multi-Threaded Server provides a production grade execution environment for code threads. These threads are developed independently and located in dynamically linked libraries available at runtime. An XML file contains information about each thread such as how many threads of each type to create and how the thread processing pipeline is constructed. A code thread may be developed in any language which creates object modules callable from a C language environment. This file is read by the UMTS at startup and the corresponding thread processing chain is created and executed. + +The Universal Multi-Threaded Server reads input data which is broken into user defined records. Input to the UMTS comes from the standard input or an optional file based interface. The developer may specify a default input routine and output routine to support non-file based i/o streams. Records formats supported are fixed length, fixed length with offset,starting/ending signature bits and a fixed length after the starting signature. The input stream does not have to be a fixed multiple of any sizes and any partial records at the end may be preserved or discarded as specified in the XML file. Once all data has been read from the input device an End of File packet is routed through the threads. + +Each input record is passed to an optional formatter routine (also defined in the xml file) which can be used by developers to reformat the input data prior to processing by the data stream. + +The Queue Service Manager provides a mechanism for dynamically routing a message between processing threads based on state information provided by each thread during its execution. Once a data packet has completed processing by the thread the processing state is recorded and the packet is dispatched to the QSM for routing to the appropriate output queue. The default queue service manager supports two pipeline based queue models, ordered and unordered pipes. In the pipeline queue model there is a one to one relationship between the input queue and the output queue. In an ordered stream the data packets are serialized at the output queue(s) to preserved the processing order. + +A default relay stub is provided to allow rapid initial deployment until development thread code lines and stubs and ready to be integrated. Processing simulation ( for early testing ) or debugging code modules can be deployed as soon as they are available. </pre>Anonymous CowardFri, 17 Jun 2011 23:07:39 -0000https://sourceforge.nete5760ba8aca9739e9dcc201741c501202e19546dhttps://sourceforge.net/p/umtsa/home/Home/Welcome to your wiki! This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage]. The wiki uses [Markdown](/p/umtsa/home/markdown_syntax/) syntax. Anonymous CowardFri, 17 Jun 2011 23:07:34 -0000https://sourceforge.net790861fa950b536f61c33454dff66d20e5b08920