You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/11/24 13:35:00 UTC
[jira] [Comment Edited] (IGNITE-6989) .NET: Thin client: Group
operation codes by purpose
[ https://issues.apache.org/jira/browse/IGNITE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265149#comment-16265149 ]
Pavel Tupitsyn edited comment on IGNITE-6989 at 11/24/17 1:34 PM:
------------------------------------------------------------------
Proposed schema:
* 0,1,... - general-purpose operations (we don't have any?)
* 100, 101, ... - cache operations
* 200, ... - quries
* 300, ... - metadata operations
was (Author: ptupitsyn):
Proposed schema:
* 0,1,2,... - general-purpose operations, OP_CACHE_GET, OP_CACHE_DESTROY, etc
* 100, 101, ... - cache operations
* 200, ... - quries
* 300, ... - metadata operations
> .NET: Thin client: Group operation codes by purpose
> ---------------------------------------------------
>
> Key: IGNITE-6989
> URL: https://issues.apache.org/jira/browse/IGNITE-6989
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.4
>
>
> Currently operation codes are in random order. Let's group things by purpose: cache operations, metadata, queries, etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)