[jboss-jira] [JBoss JIRA] Updated: (JBCLUSTER-139) Create a general purpose group RPC API

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBCLUSTER-139:
---------------------------------------

    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.

> Create a general purpose group RPC API
> --------------------------------------
>
>                 Key: JBCLUSTER-139
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-139
>             Project: JBoss Clustering
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: Q4Y7
>
>
> Abstraction on top of JGroups RpcDispatcher.
> Start with HAPartition as a base, but minus DRM and DS.  Consider what Messaging has done as well as JBCACHE-311.
> Consider separating the group membership API from the RPC API. RPC API would probably be a subinterface of the group membership one, as group RPC implies being aware of who the group is.
> This is lower priority, as, except for AS, its an internal implementation detail that can be changed.  But, AS exposes HAPartition as an API for end-user code.

-- 
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