[jboss-jira] [JBoss JIRA] (JGRP-1613) FORK: cactus stacks

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1613:
--------------------------------

Hmm... Are your components going to be created on *all* cluster nodes ? COUNTER and CENTRAL_LOCK require a coordinator to maintain cluster wide unique counters / locks. However, if we have view \{A,B,C,D\} where A's the coordinator, but the components is only created on B and D, then COUNTER / CENTRAL_LOCK won't work as they send their requests to A, which is the same as to /dev/null as the component isn't running on A...
                
> FORK: cactus stacks
> -------------------
>
>                 Key: JGRP-1613
>                 URL: https://issues.jboss.org/browse/JGRP-1613
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.4
>
>         Attachments: IMAG0129.jpg
>
>
> Introduce cactus stacks where we can have multiple, different, stacks grafted onto the same base stack. 
> The problem today is that different applications need different functionality (protocol stack configs) in the AS. For example, we have the default stack used by AS. Then, Hibernate Search wants to use distributed locking (CENTRAL_LOCK) and counting (COUNTER). The total order stack wants to use TOA/SEQUENCER and so on.
> Cactus stacks add the ability to:
> * Provide custom (partial) stacks that are grafted onto a base stack
> * Add/remove stacks at runtime
> See the attached picture for details.

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