[
https://issues.apache.org/jira/browse/MINIFICPP-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794951#comment-16794951
]
Arpad Boda commented on MINIFICPP-769:
--------------------------------------
Thread-safety is a good point. Given the fact that S2S implementation is not
threadsafe, I don't think making the repo threadsafe would worth it. In case a
user needs multithreaded Nanofi, multiple instances with multiple repos can
still be created within one process.
> In-memory content storage for Nanofi
> ------------------------------------
>
> Key: MINIFICPP-769
> URL: https://issues.apache.org/jira/browse/MINIFICPP-769
> Project: NiFi MiNiFi C++
> Issue Type: Brainstorming
> Reporter: Arpad Boda
> Assignee: Arpad Boda
> Priority: Major
> Labels: nanofi
>
> Currently Nanofi supports storing flow file content in:
> -Files (content location is a file system path)
> -C++ content repo
> The latter is planned to go away as we move towards C, however an IO-friendly
> way of processing and forwarding data would be nice.
> For eg. in case the data source is bluetooth/network/pipe, we should be able
> to provide a way of passing it through some processors and sending it via S2S
> without writing the content to local storage.
> [~phrocker] , [~aldrin] what's your opinion?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
