Having been out of touch since MiNiFi C++ got added and just getting into it, is there a reason the C++ version is trying to follow closely the MiNiFi Java version rather than just insuring connectivity with NiFi? I have not been able to find alot of details regarding the roadmap for MiNiFi C++.
It seems to me that this tight coupling is coming at the cost of the efficiency that should be gained through a C++ version. MiNiFi C++ should lend itself to a hub and spoke model with MiNiFi C++ acting as the spoke clients and NiFi as the hub. This only works, however, if maximum efficiency is maintained as spoke needs may range from servers to embedded. Additional to embedded advantages, MiNiFi C++ also has the ability to run natively as a Windows service with direct interaction with the Windows API which is also difficult at best with the Java version. Can you please provide some clarity on where things are headed? For reference, I have been through the wiki, JIRA, Confluence, Git, etc. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/DISCUSS-MiNiFi-C-0-1-0-Release-tp13956p13957.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
