ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1052) Need to implement light-weight closure execution
Date Wed, 24 Jun 2015 15:03:04 GMT

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

Atri Sharma commented on IGNITE-1052:

How difficult would it be to work in this for someone not knowing about closure executions
as is? I can take this if background research is enough to work on this...

> Need to implement light-weight closure execution
> ------------------------------------------------
>                 Key: IGNITE-1052
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1052
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Yakov Zhdanov
>            Priority: Critical
> Current run() or call() methods results in task invocation. Need to avoid this and introduce
a new way to remotely execute code
> * closure processor installs its own message listeners
> * message should contain closure to execute
> * closure is submitted to pool on arrive
> * closure takes 1 param - Grid on which it is being executed
> * when closure finishes result is sent back
> * injections should be supported
> * peer deployment should be supported
> * GridGain will not interrupt closure runner if sender leaves/fails - client can install
listener and get notification on his own. Closure is supposed to be very fast, so no need
to handle failures.

This message was sent by Atlassian JIRA

View raw message