[jboss-jira] [JBoss JIRA] (JGRP-932) Replace header names and protocol names with IDs

[Bhupesh Goel (JIRA)]

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

Bhupesh Goel commented on JGRP-932:
-----------------------------------

Bela Ban,

This change looks like has created one bug in JGroups. Earlier JGroups used to use same header name in both MuxChannel and Multiplexer classes. But with this change JGroups behavior has been changed. Now JGroups 2.12.x uses 202 and 203 IDs in MuxChannel and Multiplexer classes respectively. Since MuxChannel uses ID 202 while creating MuxHeader and Multiplexer uses ID 203 for getting MuxHeader from recieved message, we will always see "MuxHeader Not Found" issue for Multiplexer channel. 

Am i missing something here or is this really a bug?

                
> Replace header names and protocol names with IDs
> ------------------------------------------------
>
>                 Key: JGRP-932
>                 URL: https://issues.jboss.org/browse/JGRP-932
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.10
>
>
> We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. 
> A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader.
> This will solve https://jira.jboss.org/jira/browse/JGRP-872.

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