11-19-2009 12:54 PM - edited 11-19-2009 12:56 PM
Did they explain why this is necessary in your case? I would think that shared variables could do it all if you used network aliases and the stuff described here http://forums.ni.com/ni/board/message?board.id=170&message.id=363819&query.id=1281544#M363819 it would totally work if you had one pc as the host shared variable library and the other pc had a shared variable library running with all the variables binded to the ones of the first pc like it is described in that post (which may seem unrelated, but the part to pay attention to is the copy of the library with the shared variables binded to the host shared variables)
I'd just like to learn when the use of data sockets is necessary.
11-19-2009 03:54 PM
11-20-2009 03:22 PM - edited 11-20-2009 03:22 PM
If your problem was occuring with the shared variables only when connecting accross the internet then the solution I posted is the only way to do it exlusively with shared variables. It's definately an alternate solution to your problem you may want to look into in the future because shared variables are really easy to work with and all you have to do to get them to work is :
1. Create the shared variables in the usual way on the PC you want to be the host. Deploy the shared variable library.
2. Create a duplicate library (i usually add a suffix to the variable name to differentiate between host and client pc variables) and bind each variable in that library via PSP URL to the other pc. Deploy that library.
The only problem with the shared variable method is that as far as I can tell the IP of the host PC better not change. I am not sure if there is a way to dynamically bind the variables in the client PC on the fly to a new IP, but I didn't need to do that.