[
https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487315#comment-16487315
]
Otto Fowler commented on NIFI-5232:
-----------------------------------
The reason I ask: I have a PR out for an InvokeHTTP for aws gateway api
services. Part of why this concept occurred to me is the amount of replication
I had to do there.
I am wondering how this could be factored such that we have as much shared and
common as possible.
I *think* that an http execution service or service interface could be factored
such that a client could use http or aws or whatever without knowing or caring,
esp as it relates to records.
> HttpConnectionService controller service
> ----------------------------------------
>
> Key: NIFI-5232
> URL: https://issues.apache.org/jira/browse/NIFI-5232
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Mike Thomsen
> Priority: Major
>
> The functionality of InvokeHttp and related processors should be copied over
> to a controller service that can do much the same thing. This controller
> service would be able to handle all of the common scenarios with HTTP
> connections from processors going forward.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
