Feature #228
Updated by S. Wrede over 12 years ago
In order to support the We need xcfinfo / xcflogger-like introspection of RSB systems, e.g. to answer questions such as
* which participants exist at all
* which services do they expose
* to what scopes these are subscribed
* what type converters are registered
* and which processes do participants belong to
tools. This time, I'd prefer a basic distributed name service is required.
While on the long run, this may be based on sth like multicast dns or 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 request at an URI such as: rsb://about web-based software tool.
* which participants exist at all
* which services do they expose
* to what scopes these are subscribed
* what type converters are registered
* and which processes do participants belong to
tools. This time, I'd prefer a basic distributed name service is required.
While on the long run, this may be based on sth like multicast dns or 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 request at an URI such as: rsb://about web-based software tool.