[
https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797189#comment-16797189
]
Arpad Boda commented on MINIFICPP-622:
--------------------------------------
[~phrocker] :
Yes, those serve provide useful information, however I have a concern with
them: user building Nanofi is not required to execute them, so I wonder how can
we make use of them in this case. I don't think we can assume that the user is
going to build with whatever build system we provide.
That's why I was wondering on adding some of these information in Nanofi header
files - those surely get included in the USER'S BUILD.
Maybe I misunderstand something here, so fix me in that case.
> Transmit binary information for CAPI implementations in heartbeat
> -----------------------------------------------------------------
>
> Key: MINIFICPP-622
> URL: https://issues.apache.org/jira/browse/MINIFICPP-622
> Project: NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Mr TheSegfault
> Assignee: Arpad Boda
> Priority: Major
> Labels: CAPI, nanofi
>
> Heartbeats transmit a great deal of information as per our defined spec:
> [https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal]
> This ticket will be responsible for figuring out what can and cannot be sent
> via these binaries created using the CAPI
>
> For CAPI : probably need the AgentBuild information, but also potentially
> information from a consumer's program – is there a way to capture information
> about THEIR binary information
>
> May include information like python version, GCC version, etc that's NOT
> about our library ( and not captured in AgentBuild) – but rather about
> theirs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
