[ https://issues.apache.org/jira/browse/IGNITE-17257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579712#comment-17579712 ]
Alexander Lapin commented on IGNITE-17257: ------------------------------------------ [~Sergey Uttsel] LGTM to feature branch. > Implement Replica server-side logic > ----------------------------------- > > Key: IGNITE-17257 > URL: https://issues.apache.org/jira/browse/IGNITE-17257 > Project: Ignite > Issue Type: Improvement > Reporter: Alexander Lapin > Assignee: Sergey Uttsel > Priority: Major > Labels: ignite-3, transaction3_rw > > For general context please check IGNITE-17252. In addition to client > [ReplicaService|https://issues.apache.org/jira/browse/IGNITE-17257] it's > required to implement server side logic that will handle actionRequests. > Generally speaking all business related logic will be specified in > ReplicaListener, Replica or replica server itself should only handle > replication-outer action requests and propagate them to ReplicaListener, so > that it might be considered as > org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcServer / > org.apache.ignite.raft.jraft.rpc.impl.ActionRequestProcessor counterpart that > handles all business related replication-external requests. -- This message was sent by Atlassian Jira (v8.20.10#820010)