[
http://jira.jboss.com/jira/browse/JBCACHE-311?page=comments#action_12392319 ]
Manik Surtani commented on JBCACHE-311:
---------------------------------------
Approach:
1) Remove API dependencies on JGroups classes (see dependent JIRA)
2) RPCManager interface may need further fleshing out, RPCManagerImpl to be renamed to
JGroupsRPCManager
3) Move callRemoteMethods and channel ownership to the RPCManager
4) Move all callbacks and remote RPC calls to the RPCManager which will then delegate to
the actual cache.
Refactor jbosscache to provide an interface for transport
---------------------------------------------------------
Key: JBCACHE-311
URL:
http://jira.jboss.com/jira/browse/JBCACHE-311
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Nick Betteridge
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.2.0.GA
There are many different transports available (jgroups, jboss remoting etc) which are
available and which already exist within commnissioned systems. Further, clients
requirements/project specification sometimes stipulates a specific transport to be used.
JBossCache currently has JGroups embedded as the transport used. If BossCache was
refactored to provide a generic transport interface, it would make JBossCache more
'user friendly' so that the features of JBossCache can be used within a greater
variety of projects.
--
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