Determining presence of another component/peer

#1

Consider the case where component/peer A is dependent on the presence of component/peer B. As a result, we do not really want component/peer A even trying to call component/peer B until it has finished registering itself. How do we perform this level of synchronization? I don’t think subscription topics will help here but I could be wrong.

0 Likes

#2

What about a central global pool of what’s connected?

0 Likes

#3

Crossbar.io (currently) internally uses events ("I am ready") for synchronization, orchestration etc things like above.

Another direction is a router implemented "service/component registry" and stuff like service/component activation (automatic starting of components). This was discussed either on this list or on the WAMP list (dunno .. probably search for "Konstantin" .. he raised this issue) .. as a possible feature in WAMP Advanced Profile. Think SOA.

/Tobias

···

Am 22.11.2014 16:26, schrieb David Chappelle:

Consider the case where component/peer A is dependent on the presence of
component/peer B. As a result, we do not really want component/peer A
even trying to call component/peer B until it has finished registering
itself. How do we perform this level of synchronization? I don't think
subscription topics will help here but I could be wrong.

0 Likes

#4

I see. It would make a lot of sense for the router to take on this role but that sounds like a fairly involved feature. So this is what I am thinking for the time being:

This would at least give you a mechanism to synchronize components on startup. If they are all part of the same process then you don’t have to worry about offline edges. Although you could simulate one if you detected duplicate online cases.

···

On Saturday, 22 November 2014 15:44:29 UTC-5, Tobias Oberstein wrote:

Am 22.11.2014 16:26, schrieb David Chappelle:

Consider the case where component/peer A is dependent on the presence of

component/peer B. As a result, we do not really want component/peer A

even trying to call component/peer B until it has finished registering

itself. How do we perform this level of synchronization? I don’t think

subscription topics will help here but I could be wrong.

Crossbar.io (currently) internally uses events (“I am ready”) for
synchronization, orchestration etc things like above.

Another direction is a router implemented “service/component registry”
and stuff like service/component activation (automatic starting of
components). This was discussed either on this list or on the WAMP list
(dunno … probably search for “Konstantin” … he raised this issue) …
as a possible feature in WAMP Advanced Profile. Think SOA.

/Tobias

0 Likes