Confirming Norbert's suggstion about VI Server.
That approach has been avaliable going back to LV 6i. At that time it was bit more more and all you needed to do was enable VI serving on the raget machine and then knowing the path to the VI you wanted to invoke. It was THE method that was taught in early RT courses.
Since then it has been complicated by firewalls, Projects, and VI Server access lists...
I have use that approach many times ove the years becuase once you get it figured out, it abstracts away the connection and protocol complications and lets me focus on the high-level ineractions.
After the coonection is made, we need only use "Invoke Node Call by reference" to the VI we want to invoke on the target machine.
It is a elegant approach if you invoke an Action Engine on the targt machine which if properly coded, will prevent race conditions across networks with multiple nodes. I have used it to access litteraly hundreds of target machines.
There are only two draw-backs that come to mind associated with VI Server.
1) There are some that think that the VI Server appraoch is a security risk. I have built-in security checks to prevent issues in the applications that warrented the extra check.
2) The data is transfered to and from the CBR using the UI Thread so if there are large data sets being passed or recieved from, the remote machine then plan for the UI thread to be hit durring the calls.
This tag cloud has some links associated with VI server if you want to read beyond the notes in the link Norbert offered.
Ben
