[infinispan-issues] [JBoss JIRA] (ISPN-8427) Support for non-String keys in the rest server

[Gustavo Fernandes (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gustavo Fernandes updated ISPN-8427:
------------------------------------
    Description: 
The rest server assumes keys are always String, causing limited interoperability between remote endpoints.

When a cache is written via Hot Rod, by default keys will be stored as marshalled {{byte[]}} via {{JBossMarshaller}} (the default marshaller), or via UTF-8 in case the {{UT8Marshaller}} is chosen.

The Rest server should accept keys in different formats than String, using an encoding for byte[] values like Base64, and pass in an special header with the key media type so that the server can use it.

With this capability, compat mode could be avoided when writing from Hot Rod and reading from Rest and vice versa

  was:
The rest server assumes keys are always String, causing limited interoperability between remote endpoints.

When a cache is written via Hot Rod, by default keys will be stored as marshalled {{java.lang.String}} via {{JBossMarshaller}} (the default marshaller), or via UTF-8 in case the {{UT8Marshaller}} is chosen.

The Rest server should accept keys in different formats than String, using an encoding for byte[] values like Base64, and pass in an special header with the key media type so that the server can use it.

With this capability, compat mode could be avoided when writing from Hot Rod and reading from Rest and vice versa



> Support for non-String keys in the rest server
> ----------------------------------------------
>
>                 Key: ISPN-8427
>                 URL: https://issues.jboss.org/browse/ISPN-8427
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Server
>    Affects Versions: 9.2.0.Alpha1
>            Reporter: Gustavo Fernandes
>            Assignee: Gustavo Fernandes
>
> The rest server assumes keys are always String, causing limited interoperability between remote endpoints.
> When a cache is written via Hot Rod, by default keys will be stored as marshalled {{byte[]}} via {{JBossMarshaller}} (the default marshaller), or via UTF-8 in case the {{UT8Marshaller}} is chosen.
> The Rest server should accept keys in different formats than String, using an encoding for byte[] values like Base64, and pass in an special header with the key media type so that the server can use it.
> With this capability, compat mode could be avoided when writing from Hot Rod and reading from Rest and vice versa



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)