"gid"s aren't meant to be used across process groups... yet. It'll
need to be implemented.
The trade-off of using "queue_message_to_group" is if you have more
than one actor receiving that type of message in the other group, the
message will be processed by all of them.... Though you can control
message propagation by returning True or False, it isn't a solution
because you don't know which actor will get to the message first.
If you have multiple actors receiving same message in the group and
need to distinguish amongst them, you will need to control who gets
the message via their handler or via a higher level dispatcher actor.
HTH,
John
> --
> You received this message because you are subscribed to the Google Groups "pysage" group.
> To post to this group, send email to pys...@googlegroups.com.
> To unsubscribe from this group, send email to pysage+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pysage?hl=en.
>
>
My mistake then. Thanks.
> The trade-off of using "queue_message_to_group" is if you have more
> than one actor receiving that type of message in the other group, the
> message will be processed by all of them.... Though you can control
> message propagation by returning True or False, it isn't a solution
> because you don't know which actor will get to the message first.
Was counting on the same semantics applying everywhere. :)
It would be greatly beneficial if the same semantics applied using
process groups or network. Even if they were more restrictive. :)
> If you have multiple actors receiving same message in the group and
> need to distinguish amongst them, you will need to control who gets
> the message via their handler or via a higher level dispatcher actor.
This is not a problem for me!
Thanks for your quick reply!
Javier