You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/09/27 17:44:20 UTC

[jira] [Resolved] (REEF-1521) Decouple bridge handler setup and DriverStart event delegation

     [ https://issues.apache.org/jira/browse/REEF-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Markus Weimer resolved REEF-1521.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [#1095|https://github.com/apache/reef/pull/1095]

> Decouple bridge handler setup and DriverStart event delegation
> --------------------------------------------------------------
>
>                 Key: REEF-1521
>                 URL: https://issues.apache.org/jira/browse/REEF-1521
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF Driver, REEF.NET Driver
>    Affects Versions: 0.16
>            Reporter: Joo Seong (Jason) Jeong
>            Assignee: Joo Seong (Jason) Jeong
>             Fix For: 0.16
>
>
> The code for setting up Java-DotNET bridge handles ({{BridgeHandlerManager}}) and the actual delegation of DriverStart events are done in the same function ({{NativeInterop.callClrSystemOnStartHandler}}-{{JavaClrBridge::Java_org_apache_reef_javabridge_NativeInterop_callClrSystemOnStartHandler}}). These can and should be decoupled, since they do not necessarily have to be done together. Moreover, we can take the delegation of DriverStart out of the {{synchronized}} blocks so that they do not block other events from being handled. The same fix can be applied to DriverRestart events too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)