Finally - I need a stand-alone commandline program that lives on the client PC and communicates with the control.
I prefer "shared memory" for communication between the control and the commandline program.
This control must work properly, even if the customer has 10 different web pages open, all with this? control in each one, and also when the customer leaves those web pages open, "logs off", and someone else logs in to the same PC and opens more web pages with controls in them.
There is, however, only 1 "state" for all controls.? No matter how many - whatever text/variables is being displayed/set - it applies to them all at once.? (there is no individual context).
Seller must exhaustively test deliverables - buyer does not have time/resources to help with testing.
control is intended to be included in the web page via simple HTML? (eg: object or embed or similar tags)
shared memory is preferred for communication between commandline and control, however, if better technology exists for this, I'm open to suggestion.