msharee9 commented on issue #674: Minificpp 1007 - ECU C2 integration. URL: https://github.com/apache/nifi-minifi-cpp/pull/674#issuecomment-561880970 > Besides the comments added my main concern is that I still don't feel convinced about the need of implementing thread pools, message queues, ringbuffers and all the related stuff. The main reason for having threadpool is to let the user automatically start input and output processing when commanded by the c2 agent. Also, it makes using the ecu api very simple. Just two calls and the data is being forwarded. If you look at ecuapi.h, an ecu can be started using two calls if automatic processing is required, ecu = create_ecu("myecu", TAILFILE, SITE2SITE); start_ecu_context(ecu); After the ecu is started the application using the sdk won't block and the data ingestion and forwarding is started in the background in the threadpool. Ofcourse, the api is not limited to this, the user can opt to call out the functions individually to manually ingest data (some work might be needed here) and forward it if he wishes. The message queue is implemented to concurrently run the input and output processors and the ring buffer to limit the size of bufferring. The size of the buffer can be configurable (some work is needed for making it configurable).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
