[jbosscache-issues] [JBoss JIRA] Resolved: (JBCACHE-311) Refactor jbosscache to provide an interface for transport

[Manik Surtani (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCACHE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani resolved JBCACHE-311.
-----------------------------------

    Resolution: Won't Fix


> Refactor jbosscache to provide an interface for transport
> ---------------------------------------------------------
>
>                 Key: JBCACHE-311
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-311
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Nick Betteridge
>            Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira