Custom remote events can be slightly inefficient

Something we might want to improve for Hot Rod 3.0 protocol:

[16:40] <galderz> i've been thinking further about converters, and I think i've found a slight mismatch between what converter means for embedded listeners vs remote listeners
[16:40] <wburns> oh yeah?
[16:40] <galderz> for embedded listeners, it essentially transforms what you see as `value`
[16:41] <galderz> with the knowledge that key and metadata information will be shipped
[16:41] <galderz> the way i mapped converter to remote listeners is that whatever the converter returns, we ship that, as is, to the client
[16:41] <galderz> so, if a remote listener wants a custom event that includes key + value
[16:41] <galderz> it needs to develop a converter impl that returns bytes containing key + value
[16:41] <galderz> which is inefficient because you are passing around the key twice
[16:42] <galderz> once as part of the event itself, and again inside the converted value
[16:42] <galderz> inefficient from the POV of shipping stuff around from other nodes to where the cluster listener is located
[16:44] <wburns> yeah makes sense
[16:44] <galderz> not a major issue but not easy to fix without changing semantics or public protocol