Closed om26er closed 2 years ago
For rlinks the local leg starts first and then the remote leg is connected. When using in-router component, which registers a procedure, the rlink fails to start because crossbar calls this code https://github.com/crossbario/crossbar/blob/712d9da9173829be7df3ecba5dbb7981dd648fcd/crossbar/worker/rlink.py#L374, which basically tries to register all registrations on the remote end, even before the connection is made.
The solution here I believe is that the local leg shouldn't try to register procedures on the remote session and add an event handler for the remote leg's join event
join
fixed via https://github.com/crossbario/crossbar/pull/1913
oberstet
commented
2 years ago
For rlinks the local leg starts first and then the remote leg is connected. When using in-router component, which registers a procedure, the rlink fails to start because crossbar calls this code https://github.com/crossbario/crossbar/blob/712d9da9173829be7df3ecba5dbb7981dd648fcd/crossbar/worker/rlink.py#L374, which basically tries to register all registrations on the remote end, even before the connection is made.
The solution here I believe is that the local leg shouldn't try to register procedures on the remote session and add an event handler for the remote leg's
joinevent