[
https://issues.apache.org/jira/browse/MINIFI-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005285#comment-16005285
]
ASF subversion and git services commented on MINIFI-258:
--------------------------------------------------------
Commit 372f2d6f80ec040571665cea267de011e12343a2 in nifi-minifi-cpp's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=372f2d6 ]
MINIFI-258 - Removing Configure, StreamFactory, TLSContext singletons
This closes #91.
Signed-off-by: Aldrin Piri <[email protected]>
> Avoid using singleton for Configure.
> -------------------------------------
>
> Key: MINIFI-258
> URL: https://issues.apache.org/jira/browse/MINIFI-258
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
> Reporter: marco polo
> Assignee: Bryan Rosander
>
> Avoiding a singleton for Configure will allow us to eventually support
> multiple, disparate flows. The object FlowConfiguration can be passed with
> the information in Configure. This has increased coupling dramatically while
> also limiting how configurations can be stored within minifi.
> It stands to reason that to eventually support C2 activities and to
> facilitate multiple configurations, we will need to remove state from the
> global level and make it something that is referenced from the objects which
> care ( proper encapsulation ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
