[
https://issues.apache.org/jira/browse/MINIFICPP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225908#comment-16225908
]
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_r147857566
--- Diff: extensions/http-curl/client/HTTPClient.cpp ---
@@ -204,7 +264,9 @@ const char *HTTPClient::getContentType() {
}
const std::vector<char> &HTTPClient::getResponseBody() {
--- End diff --
yes and it changes again in 17...some not for the best unfortunately.
herb sutter has some really good talks about small string optimization and
how you shouldn't fight it, but I'm not too certain we can really avoid the
pessimization. what are your thoughts on the SOO causing pessimization against
strings that are larger than the buffer on things like sizeof, etc? I've seen
profiles where it can really cause unnecessary havoc.
> 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)
