[
https://issues.apache.org/jira/browse/IGNITE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778033#comment-15778033
]
Vladimir Ozerov commented on IGNITE-1680:
-----------------------------------------
Igor, my comments:
1) Let's add this manager to public {{Ignite}} API, so that user is able to
register his own extensions in runtime.
2) Extensions should be registered on per-Ignite bases, i.e. no static.
3) Let's make sure that we have sensible names. E.g. {{IgniteExtensions
Extensions()}}, {{IgniteRpc rpc()}}, {{IgniteCallbacks callbacks}}, etc..
4) We should carefully think on possible user plugins. In future we will
certainly add plugin API similar to the one we have currently in Java. So what
if user wants to register his own callback, and you do not know it's signature
in advance? So we should provide some "raw" API as well.
5) Any chance that we will be able to specify extensions in config in text
form? Or it is impossible without "refletion" in C++, and we will have to
fallback to DLL loading?
> 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)
