[jboss-jira] [JBoss JIRA] Updated: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-140?page=all ]

Brian Stansberry updated JBCLUSTER-140:
---------------------------------------

    Fix Version/s: Q4Y7
                       (was: Q4Y6)

Reducing priority on externalizing cluster project until AS 5 is out, unless there is a need related to AS 5.

Turns out JBoss Messaging did not need this.

> Examine need for a distributed service registry outside the AS
> --------------------------------------------------------------
>
>                 Key: JBCLUSTER-140
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-140
>             Project: JBoss Clustering
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: Q4Y7
>
>
> Is something like DRM needed outside the AS?  If it is, do we want to use the JBoss Cache based version (creates JBC dependency.)
> DRM is used in two ways:
> 1) To maintain a distributed registry of remote invocation targets.
> 2) To maintain a distributed registry of services, which is done by having the service register a meaningless token under its key rather than a target.  This is used by HASingleton.
> Need to examine whether this kind of thing is needed by Messaging, or whether simple listening for view changes is sufficient.  Listening for view changes could be sufficient if each group member knew how to create a Remoting InvokerLocator for the other members based on the JGroups Address.  But, this presupposes use of consistent ports across the cluster, and that the IP address used by JGroups is the one that Messaging traffic should use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira