[
https://issues.apache.org/jira/browse/MINIFI-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947714#comment-15947714
]
Aldrin Piri commented on MINIFI-239:
------------------------------------
The compatibility items are something we are going to have to figure out and
have been hinted at with MINIFI-253 and MINIFI-64. In my opinion, it would be
great to find a way to map GetHTTP into an InvokeHTTP space speaking from a
high level and something touched briefly by 64. Regardless, of all that, would
prefer to go after InvokeHTTP first.
I know [~phrocker] has been working some more framework level items, so not
sure if he has started it yet. If you were looking to address the Get/Post
gap, would encourage you to possibly take this on instead if he is not planning
on doing or has started.
> 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)
