Feature #228
Updated by J. Moringen about 10 years ago
In order to support the introspection of RSB systems, e.g. to answer questions such as
* Which which participants exist at all? (-> #44) all
* -Which which services do they expose?- expose
* To to what scopes these are subscribed (-> #44)
* What what type converters are registered
* Which and which processes do participants belong to (-> #44)
-a a basic distributed name service- an introspection protocol service is required.
In While on the long run, this may be based on something sth like multicast dns or upnp.
We upnp, we should start designing an interface that encapsulates access to the name service locally (ideally also providing callbacks when things change) and implement the access to information of other participants through a simple listener / informer pair that publishes state information -on on request at an URI such as: rsb://about-. rsb://about
* Which which participants exist at all? (-> #44) all
* -Which which services do they expose?- expose
* To to what scopes these are subscribed (-> #44)
* What what type converters are registered
* Which and which processes do participants belong to (-> #44)
-a a basic distributed name service- an introspection protocol service is required.
In While on the long run, this may be based on something sth like multicast dns or upnp.
We upnp, we should start designing an interface that encapsulates access to the name service locally (ideally also providing callbacks when things change) and implement the access to information of other participants through a simple listener / informer pair that publishes state information -on on request at an URI such as: rsb://about-. rsb://about