OOI Reactive Applicationnetwork-based data exchange programming experience. Working through this tutorial gives you an introductory understanding of the steps required to customize existing
OOI Reactive Application.
OOI Reactive Applicationsupporting producer and consumer roles simultaneously. The purpose of the
ReferenceApplicationis to demonstrate the concepts and architecture of the reactive networking application implementation, rather than to necessarily provide a realistic scenario for its use. For more extensive examples, see the Semantic-Data Processing Architecture.
ReferenceApplicationhosts parts offering
Consumerfunctionality. Both roles are implemented as independent threads that have a common graphical user interface (GUI) for diagnostic and configuration purpose.
Producersends messages containing the fields defined in the configuration file using UDP communication stack. The values are simulated. The
Consumeris configured to receive these messages from the UDP protocol stack. The
Consumerto correctly decode the messages must have configuration defining the same set of fields. The data is encoded using Variant encoding.
Consumeris covered by the document
ReferenceApplicationConsumer - Data Logger. The detailed description of the
Produceris covered by the document
ReferenceApplicationProducer - Interoperability Test Data Generator.
ReferenceApplication- an example application compliant with the Object Oriented Internet concept.
ReferenceApplication: Reactive Networking of Semantic-Data Library WPF GUI layer - it exposes the startup entry point to the runtime environment.
DataLogger: is an example of the
Consumerpart of the
Producerimplementation of a data generator to be used for testing purpose.
UDPMessageHandler: proprietary UDP
Encoding: IEncodingFactory functionality implementation limited to encoding simple data types for the testing purpose only.
ReferenceApplication.Core: this library provides an implementation of a core functionality required by the
ReferenceApplicationand all its components that are helpful in writing well-structured and maintainable applications.
UAOOI.Networking.ReferenceApplication.exeto get started.
UAOOI.Common.Infrastructurepackage. It is used to trace the behavior of libraries at run-time. To get an instance implementing this interface the
CommonServiceLocatoris used. The functionality required by the
CommonServiceLocatorhas to be provided by the hosting application. Usually, it is provided by the composition container that is built at the application bootstrap stage. To get more visit this library home page Microsoft.Practices.ServiceLocation at GitHub.
CommonServiceLocatoris not available a default logger (do nothing) is used.
UANetworkingReferenceApplication.logcaptures output messages from some public methods of the
Dnsclasses. To find the log file location click the
Actions.Open Configuration foldermenu entry.