You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2017/10/12 07:27:25 UTC

[jira] [Updated] (GEODE-3213) Refactor Protobuf Serialization Implemenation

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

Swapnil Bawaskar updated GEODE-3213:
------------------------------------
    Fix Version/s: 1.3.0

> Refactor Protobuf Serialization Implemenation
> ---------------------------------------------
>
>                 Key: GEODE-3213
>                 URL: https://issues.apache.org/jira/browse/GEODE-3213
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server, serialization
>            Reporter: Udo Kohlmeyer
>             Fix For: 1.3.0
>
>
> In the Protobuf serialization implementation, there are some refactorings we want to make:
> * OperationHandlers take OperationRequest and OperationResponse message, not the parent Request/Response Object
> * A generic flow needs to be implemented that all OperationHandlers follow. No bespoke flows for any OperationHandlers... way too much maintenance
> * Use Functional semantics to configure the functionality to extract OperationRequest from Request (per OperationHandler)
> * Use Functional semantics to configure the functionality to populate OperationResponse in the relevant Response
> * Have generic Error Handling framework to populate "known" errors and error codes



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