Multi-job scenario may have case that job 1 send messages to the proxy actor that belongs to job2.
For example, there're two jobs [Job 1] and [Job 2] that both involve party 'alice' and 'bob', a possible scenario is:
[Alice] driver submits Job1 sending messages to bob's receiver proxy and wait for response;
[Bob] for some reason, bob fails to starts the receiver proxy and then driver exit;
[Bob] driver submits Job2 where receiver proxy is listening on the same address
[Bob] Receiver proxy receives alice message which belongs to Job1, and crash.
Therefore, the cross-silo message need a job_name to distinguish. In this case, the step 4 will ignore the message.
Multi-job scenario may have case that job 1 send messages to the proxy actor that belongs to job2. For example, there're two jobs [Job 1] and [Job 2] that both involve party 'alice' and 'bob', a possible scenario is:
Therefore, the cross-silo message need a job_name to distinguish. In this case, the step 4 will ignore the message.