[infinispan-issues] [JBoss JIRA] (ISPN-313) Provide an StandaloneJGroupsChannelLookup implementation

[Mircea Markus (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786798#comment-12786798 ] 

Mircea Markus commented on ISPN-313:
------------------------------------

[~belaban] would the new jgroups protocol configuration extension (graphic?) cover this as well?
                
> Provide an StandaloneJGroupsChannelLookup implementation
> --------------------------------------------------------
>
>                 Key: ISPN-313
>                 URL: https://issues.jboss.org/browse/ISPN-313
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: RPC
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 6.0.0.Final
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira