Decoupling message based systems that communicate across a network

[drjdpowell]

I did discuss the different options with Allen Smith at NI Week and the conclusion was for command pattern across a network, the abstraction (or interface) design was the cleanest or at least easiest to understand.

Uh, my demo is command pattern over TCP.  I needed to create two new classes and four simple VIs, and if you are willing to use standard Variant/Object messages for data then you only need one class and two VIs.  One of those VIs (configuring the command with any meta info) is optional, so that leaves a single Command.lvclass:Do.vi as the only required.  

 

Surely this is simpler than any abstraction design, no?

[drjdpowell]

Here's an improved example.  The server is now a single VI, while the client registers two command-pattern envelopes, one for published "data" and one for the servers "shutdown" notification.  Each command requires one class with one method.  

 

Command Pattern Uncoupling Example2.zip

Edited January 9, 2019 by drjdpowell