[jboss-jira] [JBoss JIRA] (JGRP-1937) Configuration: revert order of protocols in configuration
Bela Ban (JIRA)
issues at jboss.org
Fri Jan 22 09:23:00 EST 2016
[ https://issues.jboss.org/browse/JGRP-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban closed JGRP-1937.
--------------------------
Resolution: Won't Do
Big resistance from the wildfly folks
> Configuration: revert order of protocols in configuration
> ---------------------------------------------------------
>
> Key: JGRP-1937
> URL: https://issues.jboss.org/browse/JGRP-1937
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
>
> Currently, a JGroups configuration lists the protocols in *bottom to top* order, e.g.
> {noformat}
> <UDP/>
> <PING/>
> ...
> <FRAG2/>
> {noformat}
> This is somewhat misleading as {{UDP}} is not the top protocol in the resulting stack, but the bottom protocol stack:
> {noformat}
> FRAG2
> |
> PING
> |
> ...
> UDP
> {noformat}
> Therefore, it would be better to define the configuration as follows:
> {noformat}
> <FRAG2/>
> ...
> <PING/>
> <UDP/>
> {noformat}
> To prevent reuse of older configurations in 4.0, we could replace {{<config>}} with {{<jgroups>}}.
> A configuration starting with {{<config>}} would be parsed in the old style (plus a warning would be issued) and a config starting with {{<jgroups>}} would be parsed in the new style.
> If programmatic configuration is used, we could check which protocol is at the head of the list. If it is a transport protocol ({{UDP}} or {{TCP}}), we could dynamically revert the order and issue a warning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list