You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Galen O'Sullivan (JIRA)" <ji...@apache.org> on 2017/12/12 18:45:01 UTC

[jira] [Updated] (GEODE-4080) Improve JSON encoding for new protocol

     [ https://issues.apache.org/jira/browse/GEODE-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galen O'Sullivan updated GEODE-4080:
------------------------------------
    Summary: Improve JSON encoding for new protocol  (was: Remove CustomEncodedValue from proto files)

> Improve JSON encoding for new protocol
> --------------------------------------
>
>                 Key: GEODE-4080
>                 URL: https://issues.apache.org/jira/browse/GEODE-4080
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server
>            Reporter: Galen O'Sullivan
>
> One of the encoding types in the new protobuf protocol is called {{CustomEncodedValue}}. However, users aren't really free to encode their own types. Also, packing JSON into a byte array is going to be harder for users than just sending ti as a string. Let's make the JSON type a string and put the custom value type in later when we actually have support for custom encoding.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)