[
https://issues.apache.org/jira/browse/MINIFI-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244279#comment-15244279
]
ASF GitHub Bot commented on MINIFI-12:
--------------------------------------
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/9#discussion_r59969390
--- Diff:
minifi-nar-bundles/minifi-framework-bundle/minifi-framework/minifi-runtime/pom.xml
---
@@ -40,6 +40,24 @@ limitations under the License.
<groupId>org.apache.nifi.minifi</groupId>
<artifactId>minifi-api</artifactId>
</dependency>
+ <dependency>
+ <groupId>ro.pippo</groupId>
+ <artifactId>pippo-core</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>ro.pippo</groupId>
+ <artifactId>pippo-tomcat</artifactId>
--- End diff --
Ah gotcha. In the interim as we are kind of prototyping things out let's
not go through solving time sinks for "optimization" at this juncture. Maybe
make another ticket to address at a later time? Implementation specifics are
hidden behind the interface so should be okay to swap.
> Network based implementation
> ----------------------------
>
> Key: MINIFI-12
> URL: https://issues.apache.org/jira/browse/MINIFI-12
> Project: Apache NiFi MiNiFi
> Issue Type: Sub-task
> Components: Data Format, Management, Processing Configuration
> Reporter: Aldrin Piri
> Assignee: Joseph Percivall
> Fix For: 0.0.1
>
>
> As an initial proof of concept for providing centralized management it would
> be advantageous to have configuration move beyond the file descriptor and
> start happening from "remote" locations. One way of doing this would be via
> simple web service from some control manager to the individual agents. A
> preliminary implementation could make use of a REST service to transmit
> information and harness the work done in MINIFI-2 as the data format to
> transfer the updates to processing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
