[
https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796445#comment-16796445
]
Aldrin Piri commented on MINIFICPP-622:
---------------------------------------
Hey [~aboda],
I am a little unclear on some of the intent items but there are a few scenarios
we need to consider. To clarify, is your current approach assuming that the
system doing the compilation will also be the host environment? I do agree
that the need to transmit this information is infrequent, but only once could
be problematic as systems evolve and are patched.
There is a construct of registration where an initial offering of information
is provided. There has been some discussion about DESCRIBE filling the area
you are talking about. Perhaps we could have a particular operand that maps to
this class of information?
> 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)
