Open AnarManafov opened 7 years ago
TaskID doesn't solve all the cases with messages sent to a wrong task. TaskID is unique for a particular task in the topology, namely, taskID is a hash of the task path in the topology. If task with the same path happens to be executed by the same agent taskID will be the same and old messages will be delivered.
A new idea with decentralized key-value probably will omit the necessity for taskID in the intercom messages.
Another option would be to generate another runtime task ID which is unique only for the lifetime of a process.
Extend Intorcom messages with destination task ID. We need to have a possibility to skip intercom messages on agents if they aren to addressed to the task the agent runs.