Hi Tst,
Thank you for your response.
Sorry to put AF question here, I was putting there but it was taking time to approve.
Approach 1: Lengthy (same I have used in my previous post's attachement)
The basic answer is that you can either pass all the messages through the caller (your green arrows)
This will be more complicated because the application I am developing is much more complex than above and code will become much lengthier.
Approach 2: Simple approch example attached
the caller can send B's enqueuer to A and A will store B's enqueuer in its data so it can send messages to it. The best approach is a topic of debate, as you can see in the discussion above and in others.
For the second approach, if your caller is different and the caller is responsible to sending the enqueuer, then the new caller will also need to send the enqueuer.
This I tried , as I am launching both A and B actors from same caller(main), I send message(B’s enqueuer) from Main actor to A actor and store this B’s enqueuer inside the while loop and use it to send message to B actor.
I like this approch simple to use but I might be missing pros and cons as warn here.
Approach 3 (Question)
The address message VI is supposed to be used when you want to an actor A to send a specific message to *some actor B* without A knowing any details about the message or about actor B. You use that VI to tell actor A about both B and the message.
I am bit curious about this approach, can you explain it more please about,
1.Where to use this ?
With my poor OO and AF knowledge, my guess is inside actor A but then
2.Do I still need to get the B’s enqueuer in A as address message.VI still needs destination’s (B’s) enqueuer ?
Thank you for help.
