[infinispan-issues] [JBoss JIRA] (ISPN-3) Should use JGroups scoping

[Bela Ban (JIRA)]

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

Bela Ban commented on ISPN-3:
-----------------------------

Yes, this still makes sense, but I don't think SCOPE should be used. Instead, here we should use the Infinispan internal thread pool which uses JGroups' Async Invocation API. If member P sends out modifications P5 and P6 for different web sessions (e.g.), then JGroups would deliver P5 and P6 sequentialy, because they're sent by the same member. Here, Infinispan could decide to deliver P5 and P6 in parallel, based on some information attached to the RPC.
                
> Should use JGroups scoping
> --------------------------
>
>                 Key: ISPN-3
>                 URL: https://issues.jboss.org/browse/ISPN-3
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: RPC
>            Reporter: Manik Surtani
>            Assignee: Vladimir Blagojevic
>
> JGroups will provide a scoping API.  This allows better concurrency in the JGroups channel.  By default, the scope used should be the cache name, although use of other scopes should be allowed such as GlobalTransaction.  Also need to consider allowing arbitrary scopes, passed in by user code.

--
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