[
https://issues.apache.org/jira/browse/IGNITE-16081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493831#comment-17493831
]
Semyon Danilov commented on IGNITE-16081:
-----------------------------------------
The prototype was developed and the concept was proven. The result is this pull
request https://github.com/apache/ignite-3/pull/534.
> Arbitrary Object Serialization Prototype
> ----------------------------------------
>
> Key: IGNITE-16081
> URL: https://issues.apache.org/jira/browse/IGNITE-16081
> Project: Ignite
> Issue Type: Task
> Components: networking
> Reporter: Sergey Chugunov
> Assignee: Semyon Danilov
> Priority: Major
> Labels: ignite-3
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *Arbitrary Object Serialization* described in
> [IEP-67|https://cwiki.apache.org/confluence/display/IGNITE/IEP-67%3A+Networking+module]
> will be used in several pieces of functionality including serialization of
> low-level network messages, in Compute Grid and Service Grid scenarios and
> some others.
> To enable early testing, clarification and integration of serialization API
> it is proposed to develop a prototype of Compute Grid functionality.
> Prototype will also enable to test code design for Compute Grid functionality
> as well.
> *Feature to be developed:*
> {code:java}
> public interface IgniteCompute {
> public <T, R> R execute(Class<? extends ComputeTask<T, R>> taskCls, T
> arg);
> }
> {code}
> It represents just the simplest method taken from existing Compute Grid in
> ignite 2.x.
> *Assumptions:*
> * No code deployment is required, all classes are available on a classpath of
> each server node.
> * Subjects of serialization are task arguments (T type) and the result (R
> type).
> * Serialization mechanism works only between server nodes. All external
> communications (thin clients etc) use independent serialization mechanisms.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
