[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JGRP-872) TP: cluster name is shipped with each message

Bela Ban (JIRA) jira-events at lists.jboss.org
Tue Sep 27 07:21:26 EDT 2011


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

Bela Ban edited comment on JGRP-872 at 9/27/11 7:20 AM:
--------------------------------------------------------

If we had a configuration file mapping cluster names to IDs, we could replace the cluster name with the ID (a short), and only send IDs around rather than strings.

If we want to do without this file, or don't find it, we could simply generate the ID as a hash of the cluster name. If 2 cluster names happen to hash to the same ID, we would accept the traffic, but most likely de-serialization would fail anyway.

      was (Author: belaban):
    If we had a configuration file mapping cluster names to IDs, we could replace the cluster name with the ID (a short), and only send IDs around rather than strings.
  
> TP: cluster name is shipped with each message
> ---------------------------------------------
>
>                 Key: JGRP-872
>                 URL: https://issues.jboss.org/browse/JGRP-872
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.1
>
>
> If a cluster name (the name used in Channel.conect()) is long, because we ship it with each message (in the TP header), this blows up the size of the marshalled messages.
> Maybe we can canonicalize the cluster name shipped with each message, similar to what we want to do with Addresses, e.g. replace the cluster name with a short.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list