[
https://issues.apache.org/jira/browse/MINIFICPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225912#comment-16225912
]
ASF GitHub Bot commented on MINIFICPP-60:
-----------------------------------------
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/158#discussion_r147858185
--- Diff: extensions/http-curl/sitetosite/HTTPProtocol.cpp ---
@@ -0,0 +1,310 @@
+/**
--- End diff --
this HTTPProtocol implementation uses CURL to do its work, hence why it
exists here. While we could certainly have cross compilation between
extensions, it doesn't seem like it's worth the increase in build time to
change. One thing I want to avoid is having single function extensions and
instead of have classes of extensions.
> Support HTTP(s) as transport mechanism for Site to Site
> -------------------------------------------------------
>
> Key: MINIFICPP-60
> URL: https://issues.apache.org/jira/browse/MINIFICPP-60
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Aldrin Piri
> Assignee: marco polo
>
> The C++ implementation would benefit from having an HTTP(S) implementation of
> Site to Site as was described in
> https://cwiki.apache.org/confluence/display/NIFI/Support+HTTP(S)+as+a+transport+mechanism+for+Site-to-Site
> and performed in NIFI-1857
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
