private vs. system message pool

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

private vs. system message pool

1,253 Views
Maciek
Contributor V

Hi,

I'm having a problem with understanding the difference (and applications) between private and system message pools. I see the difference between the private and system message queues (blocking vs. non-blocking receiving). I suppose that I can send a message to the private message queue only if the message comes from private message pool. And I can send a message to the system message queue only if the message comes from system message pool.

Am I right ?

If not - what's the difference ?

Maciek

Tags (3)
0 Kudos
Reply
1 Reply

727 Views
c0170
Senior Contributor III

Hello Maciej Saczuk,

The difference is in the logical separation of tasks that can use private pools. If a task opened a private message pool, it is the only one task that can receive messages from the pool.

  You can send message to the private queue any time if you know the pool ID. The message can be sent from any accessible memory, e.g. from a task stack. It is copied afterwards to the queue.


Regards,

MartinK