The remote iterator has internal checks for compat mode and unmarshalls keys and values before running them to the filters (in case they're present).

There should be a generic mechanism where the filter itself specifies in which format it wants to process the data. Something similar to useRawData() in the remote listeners, where each listener control the type of data should receive, either as Pojos or binary format.

Furthermode, there is a Cache Manager wide marshaller that is used to "unmarshall" filter paramers and objects. This marshaller should be removed and instead the MediaType info sent by clients should be used to select the right transcoder to convert to/from the storage format