OOI Reactive Application network-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 Application supporting producer and consumer roles simultaneously. The purpose of the ReferenceApplication is 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.ReferenceApplication hosts parts offering Producer and Consumer functionality. Both roles are implemented as independent threads that have a common graphical user interface (GUI) for diagnostic and configuration purpose.Producer sends messages containing the fields defined in the configuration file using UDP communication stack. The values are simulated. The Consumer is 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.Consumer is covered by the document ReferenceApplication Consumer - Data Logger. The detailed description of the Producer is covered by the document ReferenceApplication Producer - 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 Consumer part of the ReferenceApplication.SimulatorInteroperabilityTest: Producer implementation of a data generator to be used for testing purpose.UDPMessageHandler: proprietary UDP IMessageHandlerFactory implementation.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 ReferenceApplication and all its components that are helpful in writing well-structured and maintainable applications.Networking.ReferenceApplication of the solution UAObjectOrientedInternet.sln.UAOOI.Networking.ReferenceApplication.exe to get started.UAOOI.Common.Infrastructure package. It is used to trace the behavior of libraries at run-time. To get an instance implementing this interface the CommonServiceLocator is used. The functionality required by the CommonServiceLocator has 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.CommonServiceLocator is not available a default logger (do nothing) is used.UANetworkingReferenceApplication.log captures output messages from some public methods of the Socket, TcpListener, TcpClient, and Dns classes. To find the log file location click the Actions.Open Configuration folder menu entry.