[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=12794750#comment-12794750 ] 

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

A combination of fork-stack id and fork-channel id might do the job. E.g. with fork-stack id=2, a fork-channel picks id=17. All messages sent by that channel carry fork-stack-id=2, fork-channel-id=17. The receiver picks fork-stack 2 first, the message passes up that stack, then we pick fork-channel with id=17 and dispatch the message to it.
For messages that originate from below a fork-channel, e.g. from COUNTER, the fork-channel-id is null. 

This also works for dynamically created fork-channels: the create() call of the fork-channel carries both ids as well. If the fork-stack doesn't exist, it is created. The rest (creation and registration of the fork-channel) is the same.
                
> 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