[infinispan-issues] [JBoss JIRA] (ISPN-313) Provide an StandaloneJGroupsChannelLookup implementation
Tristan Tarrant (JIRA)
issues at jboss.org
Mon May 11 03:15:31 EDT 2015
[ https://issues.jboss.org/browse/ISPN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tristan Tarrant closed ISPN-313.
--------------------------------
Resolution: Out of Date
> Provide an StandaloneJGroupsChannelLookup implementation
> --------------------------------------------------------
>
> Key: ISPN-313
> URL: https://issues.jboss.org/browse/ISPN-313
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> StandaloneJGroupsChannelLookup would target environments that are
> either standalone or within other app servers that are not JBoss.
> It would allow for different Infinispan configurations to use the same
> shared transport, reducing network configuration.
> Infinispan and StandaloneJGroupsChannelLookup, if you guys create
> such a class, have it use the ChannelFactory.createChannel(String
> stack_name) method, not the old legacy createMultiplexerChannel method
> used by JBC. ChannelFactory.createChannel(String stack_name) will be a
> stable API, createMultiplexerChannel(...) may go away in JGroups 3.0.
> ChannelFactory.createChannel(String stack_name) lets you get a shared
> transport channel if the stack's transport protocol config has the
> singleton_name element.
> Full thread can be found in forum reference link
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the infinispan-issues
mailing list