[
https://issues.jboss.org/browse/ISPN-1326?page=com.atlassian.jira.plugin....
]
Sanne Grinovero reopened ISPN-1326:
-----------------------------------
As the cacheName is now needed to create Command instances, the
org.infinispan.commands.module.ModuleCommandFactory should pass the cacheName to the
method
{code}
org.infinispan.commands.module.ModuleCommandFactory.fromStream(String, byte,
Object[]){code}
Or implementors won't be able to create any command.
Unfortunately this is not covered by core's test suite, but you can have a look into
the Query tests (currently doesn't compile because of the field change in
_org.infinispan.commands.remote.BaseRpcCommand_
Multiplexing marshalling architecture
-------------------------------------
Key: ISPN-1326
URL:
https://issues.jboss.org/browse/ISPN-1326
Project: Infinispan
Issue Type: Enhancement
Components: Marshalling
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL
The current solution for ISPN-1205 involves sending the cache name along with each
MarshalledValue marshalled payload which is not optimal. The reason this is needed is to
be able to locate the marshaller that the MV needs, which needs to be given on instance
creation.
To make this more efficient, a multiplexing marshalling architecture is needed where the
cache name is marshalled way before anything else in the command and based on that, the
right marshaller can be picked and passed down to the externalizers to use as needed, i.e.
MarshalledValue.
The reason for doing this separately to ISPN-1205 is because some decent restructuring is
needed to get this done cos currently the cache name is embedded within the actual command
parameters, which makes it ackward to select a marshaller there and then continue
unmarshalling with that marshaller.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira