[
https://issues.apache.org/jira/browse/MINIFI-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864230#comment-15864230
]
ASF GitHub Bot commented on MINIFI-183:
---------------------------------------
Github user achristianson commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/43
@phrocker @apiri Thanks for the feedback. All makes sense, but had one
question re: civet as an ExternalProject. I did it as a thirdparty/ dir mainly
to be consistent with how the current thirdparty dependencies are handled, e.g.
yaml and leveldb. If we're OK with breaking that consistency, and perhaps
adding future tickets to extract out the current thirdparty projects, then I'll
move forward with that.
The only other concern regarding the ExternalProject is that it does make
it harder to build offline or if the remote host goes down. We would probably
want to add some build instructions for how and where to place the external
code manually to cover these build-time use cases.
> Create ListenHTTP processor
> ---------------------------
>
> Key: MINIFI-183
> URL: https://issues.apache.org/jira/browse/MINIFI-183
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: C++
> Reporter: Andrew Christianson
> Assignee: Andrew Christianson
>
> Create a ListenHTTP processor of similar design/function to the ListenHTTP in
> the parent Apache NiFi project.
> Being a part of MiNiFi, the server should be very lightweight, handle
> requests asynchronously, have optional threading, and should support
> streaming of request/response content to minimize memory requirements.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
