[
https://issues.apache.org/jira/browse/IGNITE-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152216#comment-16152216
]
Pavel Tupitsyn edited comment on IGNITE-6236 at 9/4/17 9:00 AM:
----------------------------------------------------------------
1) I think we have decided to include some flags in every message, see parent
ticket and related dev list discussion.
2) Let's do exception handling as a separate ticket: IGNITE-6250
3) On the protocol level this looks simpler to me. Operation succeeded? Write
1. Otherwise 0. Why would I write a pointless type code here?
4) {{CacheTestNoMeta}} added: it uses no-op binary processor, disabled compact
footers and unregistered binary type format (where type name is included in
binary object header). Cache operations on such objects (including SQL) work
both from client and server.
5) Done
was (Author: ptupitsyn):
1) I think we have decided to include some flags in every message, see parent
ticket and related dev list discussion.
2) Let's do exception handling as a separate ticket.
3) On the protocol level this looks simpler to me. Operation succeeded? Write
1. Otherwise 0. Why would I write a pointless type code here?
4) Ok, let's see if we can work without metadata in this ticket and handle that
later.
5) Ok.
> .NET: Thin client: cache.Get and Put for user types
> ---------------------------------------------------
>
> Key: IGNITE-6236
> URL: https://issues.apache.org/jira/browse/IGNITE-6236
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> Cache operations on user types require proper metadata handling. Make sure
> dynamic type registration works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
