@JÞB wrote:
@mcduff wrote
@JÞB wrote:
I would say it is "permissible" to send a request to a producer to "Send Stop Message to all Consumers,"( or any message) with or without priority, from other areas of a program.
Why have a "middle man"? Not sure I see any significant advantages of have a two layered message approach.
Honestly, that "This Consumer Expects Only 1 Producer Endpoint" is not a hard and fast rule for the consumer loops that YOU write. However, when the other developers that start spawning other processes consuming the same commands and those commands are coming from "Wherever willy-nilly" and have no single source vi to clarify what messages may exist. Someone is going to prefer to swear at you rather than buy you a beer after they fail to code a case to handle that interjected message.
Clear?
Agree to disagree. I normally program alone so don't have that issue, but I can see the issue you are presenting. For me, I prefer 1 wire (User Event) that can go anywhere in the program and message anywhere in the program. For me, I got frustrated spawning new queues for loops, then having to keep track of those queues, etc. Even when code reviewing a LabVIEW Architect's code, trying to following queues nested in subVI's and where they were going was difficult.
