geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3213) Refactor Protobuf Serialization Implemenation
Date Tue, 18 Jul 2017 16:30:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091791#comment-16091791
] 

ASF subversion and git services commented on GEODE-3213:
--------------------------------------------------------

Commit cdd8510b863e420e8af69993464a4a0936509c93 in geode's branch refs/heads/feature/GEODE-3213
from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=cdd8510 ]

GEODE-3213: Adding Result object to avoid handling errors in special way


> 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
>
> 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)

Mime
View raw message