msharee9 commented on issue #734: MINIFICPP-1157 Implement lightweight C2 heartbeat. URL: https://github.com/apache/nifi-minifi-cpp/pull/734#issuecomment-585369988 > @msharee9 Could you have a different endpoint that is used for a full posting and then another endpoint for a lightweight HB. The period for those could be different or the full posting could be sent only once ( with success validation ). > > Another alternative is to have the C2 server request a full posting and then the registration occur in that case and otherwise always be a light weight HB. That may alleviate some of the complexity per @arpadboda The full posting is done only once in this code change and that is during C2 initialization and after that it is lightweight both going to the same endpoint though. I don't think it would work best from C2 server standpoint if we want to send to two different endpoints. Sending the heartbeat during initialization is an optimization (thanks to @szaszm suggestion), otherwise, the original idea was to only send manifest when C2 server requests for it in DESCRIBE and always send lightweight heartbeats always. In case the first heavyweight heartbeat is lost due to some reason, the C2 server will request manifest anyhow upon first successful reception of lightweight heartbeat.
---------------------------------------------------------------- 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
