[jira] [Commented] (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:comment-tabpanel=16427828#comment-16427828 ] ASF subversion and git services commented on GEODE-4961: Commit 049e10abac58b8123fe5fb148fd1fb11de8a276b in geode's branch refs/heads/feature/GEODE-4624 from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=049e10a ] GEODE-4961: Allowing custom serialization formats with the protobuf protocol Adding a new ValueSerializer interface that users can implement to control the serialization format of data sent using the protobuf protocol. ValueSerializers are registered on the server side using the java ServiceLoader mechanism. They are selected by the client using a new valueFormat field in the handshake. Renamed AuthenticationRequest to HandshakeRequest. Credentials and valueFormat are all sent as part of a single HandshakeRequest. Renamed the connection states to make them a little easier to understand, and removed some duplicate states. The new states are RequireVersion, RequireAuthentication, AcceptMessages, InvalidSecurity, and TerminateConnection > 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 > 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)
[jira] [Commented] (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:comment-tabpanel=16427553#comment-16427553 ] ASF subversion and git services commented on GEODE-4961: Commit 049e10abac58b8123fe5fb148fd1fb11de8a276b in geode's branch refs/heads/develop from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=049e10a ] GEODE-4961: Allowing custom serialization formats with the protobuf protocol Adding a new ValueSerializer interface that users can implement to control the serialization format of data sent using the protobuf protocol. ValueSerializers are registered on the server side using the java ServiceLoader mechanism. They are selected by the client using a new valueFormat field in the handshake. Renamed AuthenticationRequest to HandshakeRequest. Credentials and valueFormat are all sent as part of a single HandshakeRequest. Renamed the connection states to make them a little easier to understand, and removed some duplicate states. The new states are RequireVersion, RequireAuthentication, AcceptMessages, InvalidSecurity, and TerminateConnection > 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 > 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)
