MultiValue Communications: The Persnickety Persistence Problem
For decades, MultiValue applications have followed the model of having an always active, persistent connection to the server. This worked well when we had control over the connection, primarily by using a dedicated cable to a serial RS-232 port physically located on a board in the machine. Then came networks, where everything is dynamic and out of our control. Yet in 2011, how many of our MultiValue application still stick to trying to emulate the old persistent connection model of the last century?