[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:all-tabpanel ]

Bela Ban updated JGRP-1613:
---------------------------

    Fix Version/s: 3.4
                       (was: 4.0)


OK, based on a conversation with Sanne at Red Hat Summit, we decided to narrow the scope:
* FORK can only be the top protocol in a stack (or towards the top of the stack)
* An app gets a call createChannel() which takes a string that as to be unique
* That string is used to mux/demux messages to the app
* A header is added to each message including that max-id so we know how to mux/demux
* There is a *main channel* and the dynamically created channels refer to it, e.g. their lifetime is less than or equal to the main channel
* When the main channel is closed, sending of messages on the fork-channel throws an exception
* The view and address of the fork-channels is the same as that of the main channel
                
> 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