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/04/09 01:45:25 UTC

[jira] [Updated] (REEF-1069) Revisit IClock/RuntimeClock

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

Markus Weimer updated REEF-1069:
--------------------------------
    Component/s: REEF.NET

> Revisit IClock/RuntimeClock
> ---------------------------
>
>                 Key: REEF-1069
>                 URL: https://issues.apache.org/jira/browse/REEF-1069
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET
>            Reporter: Julia
>
> Currently in .Net several public methods are not define at IClock level but RuntimeClock, that enforces the code to use subclass instead of interface/abstract class. 
> For example, in EvaluatorSettings, we have to inject RuntimeClock instead of IClock. 
> Once the proper methods are defined at base level, we should then change  RuntimeClock into IClock in EvaluatorSettings constructor and set RuntimeClock as a default implementation of IClock. 



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