You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexandr Shapkin (Jira)" <ji...@apache.org> on 2019/10/15 16:49:00 UTC

[jira] [Updated] (IGNITE-12293) Thin client: config serialization should use OpCodes

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

Alexandr Shapkin updated IGNITE-12293:
--------------------------------------
    Summary: Thin client: config serialization should use OpCodes  (was: .NET thin client: config serialization should use OpCodes)

> Thin client: config serialization should use OpCodes
> ----------------------------------------------------
>
>                 Key: IGNITE-12293
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12293
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 2.7.6
>            Reporter: Alexandr Shapkin
>            Assignee: Alexandr Shapkin
>            Priority: Major
>              Labels: platforms
>             Fix For: 2.9
>
>
> Thin client configuration could be partially serialized via ClientCacheConfigurationSerializer.java
> But this #OpCode based serialization is limited only to .NET -> Java direction.
> Let's use OpCodes as a default implementation for all supported platforms, this will help us to add a new configuration section only for a specific platform.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)