[ https://issues.jboss.org/browse/JGRP-809?page=com.atlassian.jira.plugin.s... ] Sanne Grinovero commented on JGRP-809: -------------------------------------- Hi Bela, personally I'm mostly looking forward for the public API changes of JGroups to accept a reference to a buffer rather than having {code}byte[]{code} all over. In several cases I actually deal with off-heap memory in the application code (sometimes plain old files), and I have to copy things into byte arrays to satisfy the JGroups API; if we could pass these things to you by reference, I suspect you could avoid some copying, chunking, resizing.. even if at wire level you actually end up needing to make some copies to satisfy limitations of latest NIO APIs. Since you're working on a major release, I'd focus on shaping the JGroups API. Allow applications interacting with JGroups to define what they want transmitted without actually allocating memory: postpone buffer massaging as much as possible, you'll then be able to evolve the low level details in the near future without imposing disruptive changes to client code. I guess that even with Socker limitations, there might still be cases in which you could avoid the copies? In some other cases, maybe the whole operation has to be aborted.. such cases would be an implementation detail, and we could refine that iteratively ; hopefully having the basic stuff put in place, we should all be able to start empirical iterations and help making the "details" evolve in smaller steps. -- This message was sent by Atlassian JIRA (v6.3.15#6346)