[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1259) Reduce size of large headers: place data into message itself

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1259.
----------------------------

    Resolution: Deferred


Won't do this for the reasons outlined in the comments. However, this is a good practice for some selected protocols. E.g. RELAY uses this. But it has to be the only protocol that's serialing into the payload, or else different protocols would overwrite each other's data.

> Reduce size of large headers: place data into message itself
> ------------------------------------------------------------
>
>                 Key: JGRP-1259
>                 URL: https://issues.jboss.org/browse/JGRP-1259
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.12
>
>
> When we send a view around, we essentially create an empty Message and attach a GmsHeader.VIEW with the new view.
> If the view consists of 200 members, the view header will be very big and the message is still empty (null buffer).
> The issue here is that FRAG2 only fragments the message's buffer (this is faster), and so a huge header might add so much to the size of a serialized message that the transport (UDP) won't be able to send it !
> SOLUTION: still use the header (e.g. GmsHeader.VIEW), but place potentially large payloads into the message. This will allow FRAG2 to fragment the message very efficiently.

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