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 2018/10/02 07:10:00 UTC

[jira] [Resolved] (GEODE-4961) Add a customizable value encoding to the protobuf protocol

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

Galen O'Sullivan resolved GEODE-4961.
-------------------------------------
       Resolution: Done
    Fix Version/s: 1.6.0

> Add a customizable value encoding to the protobuf protocol
> ----------------------------------------------------------
>
>                 Key: GEODE-4961
>                 URL: https://issues.apache.org/jira/browse/GEODE-4961
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> All values sent using the protobuf client/server protocol are currently encoded using JSON if they are not primitives.
> Users may want to serialize their objects in some other format than JSON. In order to accomplish this, we should add a way to control the serialization format.
> We can do this by adding the CustomValueSerializer described in this wiki page - [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75975878]
> We should also add support to the geode-experimental-driver module to allow users of  that driver to customize the serialization of their objects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)