[
https://issues.jboss.org/browse/ISPN-8099?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-8099:
-------------------------------------
Do we intend to limit the types of these parameters to a short list of primitives (the
ones that are already used internally by the HR protocol spec)? Otherwise I cannot see how
could one design an agnostic format for them. Anything beyond simple types would require
the help of the marshaller, actually it would require the help of the encoders that we
introduced recently.
Hot Rod filter/converter parameters should use marshaller agnostic
formats
--------------------------------------------------------------------------
Key: ISPN-8099
URL:
https://issues.jboss.org/browse/ISPN-8099
Project: Infinispan
Issue Type: Enhancement
Components: Remote Protocols
Reporter: Tristan Tarrant
Assignee: Galder ZamarreƱo
The filters/converters resort to the configured marshaller to interpret parameters. We
should favour an agnostic format.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)