[
https://issues.apache.org/jira/browse/IGNITE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831382#comment-15831382
]
Vladimir Ozerov commented on IGNITE-1680:
-----------------------------------------
[~isapego], personally I do not like {{IgniteRpc}} much because this is not
really {{RPC}} in usual sense. We do not have stubs, proxies, etc.. We do not
have an aim to abstract out local and remote execution modes in a single API.
To be more precise, we do have this goal in mind for compute API, but this is
not the case for other stuff like continuous queries. I thought that
{{IgniteRemoting}} could be good candidate, but this is essentially a synonym
to {{IgniteRpc}}.
What we really do with this API is {{linking}} Ignite code with user code. But
{{linker}} or {{linkage}} words might confuse CPP users. So I think that word
{{bind}} explains API goals best. So let's consider something around this word:
- {{IgniteBinding}}
- {{IgniteBindings}}
- {{IgniteBinder}}
> CPP: Implement basic API for user entry point lookup
> ----------------------------------------------------
>
> Key: IGNITE-1680
> URL: https://issues.apache.org/jira/browse/IGNITE-1680
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Igor Sapego
> Assignee: Vladimir Ozerov
> Labels: cpp, roadmap
> Fix For: 2.0
>
>
> Need to implement IgniteCompute class for C++ with one basic method
> IgniteCompute::Call(...) which will provide basic remote job execution API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
