Repository: nifi-minifi-cpp Updated Branches: refs/heads/master 5d5a56227 -> 9336e1e34
MINIFICPP-635: Resolve typos Project: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/repo Commit: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/commit/9336e1e3 Tree: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/tree/9336e1e3 Diff: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/diff/9336e1e3 Branch: refs/heads/master Commit: 9336e1e34d3f5982ad99fb8625badd1c699ab8d7 Parents: 5d5a562 Author: Marc Parisi <[email protected]> Authored: Fri Oct 5 18:13:21 2018 -0400 Committer: Aldrin Piri <[email protected]> Committed: Thu Oct 11 15:45:28 2018 -0400 ---------------------------------------------------------------------- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/blob/9336e1e3/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index a59589d..1277934 100644 --- a/README.md +++ b/README.md @@ -799,9 +799,9 @@ created within the build directory that contains a manifest of build artifacts. The build identifier will be carried with the deployed binary for the configuration you specify. By default all extensions will be built. -### Managing MiNFI C++ through the MiNiFi Controller +### Managing MiNiFi C++ through the MiNiFi Controller -The MiNiFi controller is an executable in the bin directory that can be used to control the MiNFi C++ agent while it runs. Currently the controller will let you stop subcomponents within a running instance, clear queues, get the status of queues, and update the flow for a warm re-deploy. +The MiNiFi controller is an executable in the bin directory that can be used to control the MiNiFi C++ agent while it runs -- utilizing the [Command and Control Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal). Currently the controller will let you stop subcomponents within a running instance, clear queues, get the status of queues, and update the flow for a warm re-deploy. The minificontroller can track a single MiNiFi C++ agent through the use of three options. Port is required. The hostname is not and will default to localhost. Additionally, controller.socket.local.any.interface allows
