Return-Path: <issues-return-30419-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id E1D51200BEA
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 27 Dec 2016 13:31:59 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id E07D5160B31; Tue, 27 Dec 2016 12:31:59 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 34368160B23
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 27 Dec 2016 13:31:59 +0100 (CET)
Received: (qmail 2775 invoked by uid 500); 27 Dec 2016 12:31:58 -0000
Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ignite.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ignite.apache.org>
List-Post: <mailto:issues@ignite.apache.org>
List-Id: <issues.ignite.apache.org>
Reply-To: dev@ignite.apache.org
Delivered-To: mailing list issues@ignite.apache.org
Received: (qmail 2764 invoked by uid 99); 27 Dec 2016 12:31:58 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Dec 2016 12:31:58 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 534A02C03DC
	for <issues@ignite.apache.org>; Tue, 27 Dec 2016 12:31:58 +0000 (UTC)
Date: Tue, 27 Dec 2016 12:31:58 +0000 (UTC)
From: "Igor Sapego (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12904870.1444829886000.599620.1482841918336@Atlassian.JIRA>
In-Reply-To: <JIRA.12904870.1444829886000@Atlassian.JIRA>
References: <JIRA.12904870.1444829886000@Atlassian.JIRA> <JIRA.12904870.1444829886459@arcas>
Subject: [jira] [Comment Edited] (IGNITE-1680) CPP: Implement basic API for
 user entry point lookup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 27 Dec 2016 12:32:00 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715245#comment-15715245 ] 

Igor Sapego edited comment on IGNITE-1680 at 12/27/16 12:31 PM:
----------------------------------------------------------------

Ok, here is concept that I have implemented and checked:
{code}
// If user has any jobs, processors or other classes, that
// may be invoked by the remote side, they should be registered
// in the following function. Every module should have no more
// than one function with the following signature. This function
// called by Ignite when module is loaded.
IGNITE_EXPORTED_CALL void IgniteModuleInit(ignite::InvokeManager& im)
{
    im.RegisterCacheEntryProcessor<UserProcessor1>();
    im.RegisterCacheEntryProcessor<UserProcessor2>();

    im.RegisterJob<UserJob1>();
    im.RegisterJob<UserJob2>();
	
    ...
}

// User classes should implement corresponding Ignite classes and 
// have static methods, that return class id. Something like:
class UserProcessor1 : public CacheEntryProcessor<...>
{
    // User implements CacheEntryProcessor interface here...
	
    // Function, that return some unique ID for the class.
    static int64_t GetIgniteId()
    {
        ...
    }
}
{code}

What do you guys think?


was (Author: isapego):
Ok, here is concept that I have implemented and checked:
{code}
// If user has any jobs, processors or other classes, that
// may be invoked by the remote side, they should be registered
// in the following function. Every module should have no more
// than one function with the following signature. This function
// called by Ignite when module is loaded.
IGNITE_EXPORTED_CALL void IgniteModuleInit(ignite::InvokeManager& im)
{
    im.RegisterCacheEntryProcessor<UserProcessor1>();
    im.RegisterCacheEntryProcessor<UserProcessor2>();

    im.RegisterJob<UserJob1>();
    im.RegisterJob<UserJob2>();
	
    ...
}

// User classes should implement corresponding Ignite classes and 
// have static methods, that return class id. Something like:
class UserProcessor1 : public CacheEntryProcessor<...>
{
	// User implements CacheEntryProcessor interface here...
	
	// Function, that return some unique ID for the class.
	static int64_t GetIgniteId()
	{
		...
	}
}
{code}

What do you guys think?

> 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: Igor Sapego
>              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)