[
https://issues.apache.org/jira/browse/GEODE-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298812#comment-16298812
]
ASF subversion and git services commented on GEODE-4080:
--------------------------------------------------------
Commit e24e038e69244cc655779634945896411e678080 in geode's branch
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e24e038 ]
GEODE-4080: Protobuf JSON objects are in a proto string (#1171)
* GEODE-4080: Protobuf JSON objects are in a proto string
In the process, remove a couple of serialization-related classes that
are no longer really applicable.
* Catch `JSONFormatterException` and return it as a `EncodingException`.
* Change some names and add ProtobufSerializationService, which is the big
reason for all this churn.
* Get rid of the codec package
* Inline the serialization type enum
* Make encoding methods throw EncodingException.
* Don't use exceptions for control flow.
This meant renaming ProtobufPrimitiveTypes to ProtobufEncodingTypes.
Signed-off-by: Brian Rowe <[email protected]>
> 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)
