[
https://issues.apache.org/jira/browse/NIFI-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012979#comment-15012979
]
Tony Kurc commented on NIFI-1086:
---------------------------------
[~joewitt] - I was on the fence about this, as there are other general purpose
utils in standard processor utils already. I think for 1.0.0, there probably
should be a consolidation of these utils, as well as considering what apache
commons may provide (e.g. IOUtils and OS detection in commons-lang). In the
spirit of timeliness (pending release), I weighed "going with the code we had"
vs potentially adding some tech debt to consolidation as it was holding up two
features. If you think I made the wrong call, SOON would be the time to move it.
> Refactor InvokeHttp
> -------------------
>
> Key: NIFI-1086
> URL: https://issues.apache.org/jira/browse/NIFI-1086
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
> Fix For: 0.4.0
>
> Attachments: NIFI-1086_02.patch, NIFI-1086_03.patch,
> NIFI-1086_04.patch, NIFI-1086_05.patch, NIFI-1086_rebasing_to_master.patch
>
>
> InvokeHttp currently uses Java's HttpUrlConnection, which is lacking in it's
> features and ease-of-use. In order to support all the current InvokeHttp
> pending tickets it's clear that a new underlying library is needed.
> OkHttp looks to be a promising library that focusing on individual
> transactions (as opposed to Apache's HttpClient that focuses more on
> sessions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
