[
https://issues.jboss.org/browse/ISPN-8004?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-8004:
-------------------------------------
I suppose sending the class name would solve the problem, but we want to send a numerical
id instead to save some bandwidth. Could we use in internal cache as a replicated registry
that maintains the mapping of encoder internal numerical id to class name (and the
reverse)? Or what approach do you have in mind? I would like to avoid solutions that
leave the assignment of ids to the users, like it happens with externalizers now.
Optimize serialization of encoders
----------------------------------
Key: ISPN-8004
URL:
https://issues.jboss.org/browse/ISPN-8004
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 9.1.0.CR1
Reporter: Gustavo Fernandes
Certain cache operations such streams, compute and functional commands require shipping
the current associated encoder/wrapper to the cache instance to remote nodes.
Currently, the Class<?> representing the encoder is sent over the wire, both for
the key and for the value. It should be possible to associate an id to each
encoder/wrapper and sent those instead
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)