Menu:

Links:

EOS Splitter Service

The EOS model specifies that EOS readers make outbound connections to EOS hosts. By design, a single EOS reader is limited to connecting to a single EOS host. It is not currently possible for multiple EOS hosts to receive EOS notifications from the same reader. The EOS Splitter is a middleware application that overcomes this limitation.

Essentially, the EOS Splitter is a Windows service which accepts multiple inbound connections from EOS Readers and mirrors its data to multiple outbound channels, sort of like a many-to-many repeater.

This is useful when you need to receive EOS notifications from multiple readers at multiple destinations as is the case with debugging. A typical debugging scenario would be setting up an outbound channel to OAT or Device Commander and another outbound channel to the EOS service tool. All inbound data is sent to all outbound channels. This lets us spy the data being sent to OAT or Device Commander using the EOS Service Tool. There is no limitation on the number of outbound channels.

In addition to mirroring network connections, the EOS Splitter has the ability to call custom code implemented as plugins. Plugins are the main point of extensibility in the system and give the user the ability to create and add functionality of their own design. This is useful when you simply want to perform some action when an EOS notice is received, e.g., parse the notice and populate a database. A sample plugin with source code is provided. There is no limitation on the number of plugins.

A Network Monitor has just been added to the EOS Splitter. When running on the same machine as another application or middleware, the EOS Splitter has the ability to eavesdrop on the conversation and mirror its notifications. This is useful when you simply want to debug an existing connection without reconfiguring the hardware.

Finally, The EOS Splitter completes the EOS model by allowing multiple clients to connect to the service using .NET Remoting. This is useful when you want to create temporary connections as is the case with EOS Monitoring.

Channels, Plugins, .NET Remoting and Network Monitoring can all be used at the same time.

Once configured, the EOS Splitter can be set to start automatically and does not require the user to be logged into the machine.

For demonstration purposes, a host application, the EOS Notice Counter, is provided.