Any idea, how WaitforUpdate() would behave if calling from different thread using same property collector ?
And to use different property collector in different thread, do we require different sessions per thread ?
Any clue on these topics or any docs which says about how VI SDK behave in multi threaded application would be helpful.
Check out Monet. It should be pretty easy to test your question from within the context of that app. FYI - Monet logs in to the SDK on one thread and waits for updates on the other, so it does work, although I cannot guarantee synchronization.
I work with a heavily threaded application and this has never been an issue for the SDK. This includes the WaitForUpdate() call, which is a natural to spin off separately.
Thanks Tom for reply.
Any docs or KB which says how sdk api works in multithreading enviornment ? Because we are suspecting some issues in API due to multithreading.
I dont know if there is any specific doc on this. Communication with the VI webservice behaves as any other web application, so possibly there is no need for this. What exactly are you looking for? Please provide some more info on what you are doing and what error is coming up.
p.s. I have never experienced any multihreading related issues either...
We have similar query about waitforupdate, can we make waitforupdate and other VI API like "queryAvailablePerfMetric" call concurrently in two different threads using single(same) session.
Can Server (VC) accepts multiple requested (VI SDK calls) concurrently on same session?