Allow remotable services to scope to one or more service groups
---------------------------------------------------------------
Key: AMDATU-259
URL: http://jira.amdatu.org/jira/browse/AMDATU-259
Project: Amdatu
Issue Type: New Feature
Components: Amdatu Sevice Fabric
Reporter: Bram de Kruijff
In the current implementation of the DistributionService every instance
considers any service the publishes export service registration properties as
defined by the Remote services spec (intents mostly). As in an Amdatu container
multiple DistributionServices may be active, each operating for a specific
service group this at present effectively means that any remotable service will
be published in every service group and subsequently remoted y the
corresponding DiscoveryService. This kind of negates the purpose of service
groups.
Therefore we must allow any service to specify the service group(s) it is
relevant for. This must be done based on service registration properties wich
are then considered by the Distribution and/or Discovery services. Question
remaining is wether we implement it as an intent (which is not really intended
as a name/value thingy and might frustrate with a 3rd party impl) or
introducing a custom Amdatu service registration property. I think the latter.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
