[
https://issues.apache.org/jira/browse/MINIFI-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949090#comment-15949090
]
marco polo commented on MINIFI-239:
-----------------------------------
[~achristianson] I think there is a decent amount of work to reach parity.
Testing is certainly needed, but I think we probably need security, more
functionality for types of encoding, etc...though it stands to reason that we
could incrementally provide functionality. I'm gonna jump on rebasing against
master now so that it's a bit cleaner for an eventual merge. We finally merged
the namespace changes so that incurred a bit of "churn" in the tickets that I'm
currently working.
> Create a C++ HTTP client processor to match the InvokeHTTP processor
> --------------------------------------------------------------------
>
> Key: MINIFI-239
> URL: https://issues.apache.org/jira/browse/MINIFI-239
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: C++, Extensions
> Reporter: Andrew Grande
> Assignee: marco polo
>
> There is a ListenHTTP processor, but nothing for the client side (e.g. to
> invoke REST APIs). The civetweb library is already being used, can be
> leveraged to implement the InvokeHTTP parity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
