[
https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797073#comment-16797073
]
Mr TheSegfault commented on MINIFICPP-622:
------------------------------------------
Have you seen generateVersion.sh and generateVersion.bat ? These linked
libraries should be embedded at build time and send much like the current agent
build information is sent. There certainly could be additional information
needed that can only be provided via the construction of said interfaces.
> 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)
