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/09/06 12:30:00 UTC

[jira] [Updated] (IGNITE-6279) .NET: Decouple AbstractQueryCursor from PlatformTarget data exchange specifics

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

Pavel Tupitsyn updated IGNITE-6279:
-----------------------------------
    Description: {{AbstractQueryCursor}} should be concerned only with iterator and cursor logic. Data exchange should be factored out. This will simplify code reuse for thin client.  (was: {{AbstractQueryCursor }} should be concerned only with iterator and cursor logic. Data exchange should be factored out. This will simplify code reuse for thin client.)

> .NET: Decouple AbstractQueryCursor from PlatformTarget data exchange specifics
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-6279
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6279
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .NET
>             Fix For: 2.3
>
>
> {{AbstractQueryCursor}} should be concerned only with iterator and cursor logic. Data exchange should be factored out. This will simplify code reuse for thin client.



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