[
https://jira.jboss.org/jira/browse/JBCLUSTER-139?page=com.atlassian.jira....
]
Brian Stansberry commented on JBCLUSTER-139:
--------------------------------------------
This is necessary for the Infinispan conversion, as the session ownership locking code
needs it (the locking will not be HAPartition based; will be built on JGroups' new
shared RpcDispatcher.
Also, this allows the RPC API to be cleaned up by converting return types from ArrayList
to List<?>. HAPartition can override the superinterface methods to still return
ArrayList, making it compatible with existing users. Internal stuff can use the
superinterface API.
Create a general purpose group RPC API
--------------------------------------
Key: JBCLUSTER-139
URL:
https://jira.jboss.org/jira/browse/JBCLUSTER-139
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: HA-Server-API
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: HA-Server-API 2.0.0.Beta1
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira