I’m working on a program being developed using AF, to be run on a cRIO.
Later in this project one of our partner companies will be developing a similar program, and while they don’t want my code, they want one arm of its functionality. However, they don’t intend on using actor framework to develop. So I need to be able to wrap up my module in some way and give it to them and it just be able to spit out data into their code.
The example here of converting the actor into a by-reference object and having the data accessed through a DVR seems fine, but elsewhere I’ve seen network endpoints recommended. I suppose in this case my module would stay as a separate program to theirs, rather than being dropped into their code.
Would one approach be preferable to the other considering that both the actor and non-actor code need to be running and communicating on the same cRIO? Maybe it doesn't change much, but just want to check
(the speed and determinism of the cRIO aren’t important)
