[
http://jira.jboss.com/jira/browse/JBCACHE-311?page=all ]
Manik Surtani updated JBCACHE-311:
----------------------------------
Fix Version/s: 4.0.0
(was: 3.0.0)
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref
Guide, User Guide, etc.)])
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
Fix For: 4.0.0
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