[
https://issues.apache.org/jira/browse/MINIFICPP-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840898#comment-16840898
]
Mr TheSegfault edited comment on MINIFICPP-673 at 5/16/19 1:36 AM:
-------------------------------------------------------------------
[~aboda] I began working on this and found the API could do well with some
minor improvements ( though in whole I love it ). I've created some tickets
regarding these aspects of it, which are hopefully discussion points. I've
unassigned this from you for the time being since you've taken on a much larger
task with OPC-UA and I've started a POC for this.
was (Author: phrocker):
[~aboda] I began working on this and found the API could do well with some
minor improvements ( though in whole I love it ). I've created some tickets
regarding these aspects of it. I've unassigned it from you for the time being
since you've taken on a much larger task with OPC-UA
> Define ECU (Edge Collector Unit )
> ---------------------------------
>
> Key: MINIFICPP-673
> URL: https://issues.apache.org/jira/browse/MINIFICPP-673
> Project: Apache NiFi MiNiFi C++
> Issue Type: Epic
> Reporter: Mr TheSegfault
> Priority: Major
> Labels: ECU, nanofi
> Fix For: 0.7.0, 0.8.0
>
>
> Edge Collector Units ( ECU ) will be minimized agents whose sole focus is
> collection and retrieval of data. Defined as feature facing constructs, ECUs
> will define functionality that is agnostic of system. We'll build the
> portability behind the library.
>
> [~aboda] This ticket encompasses building software from individual units of
> functionality. So take the log aggregation example in MINIFICPP-621 . There
> we have an instance of "tail file" linked to site to site. To do this will
> require the ability to link these units ( we've called them building blocks,
> but that's more documentation ), stream data between them, and then define
> success and failure conditions ( or relationships ).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
