[
https://issues.apache.org/jira/browse/MINIFICPP-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846774#comment-16846774
]
Mr TheSegfault commented on MINIFICPP-877:
------------------------------------------
Thanks, the KNOWN_BUGS in docs makes the interpretation much clearer, as do the
related tickets. It's open source, so unless someone wants to work on those
changes, admittedly it is what it is. In which case we can assume that the
initializer will initialize both. Since TLSSocket is guaranteed to initialize
after these initializers, where does the thread safety issue originate other
than another extension?
> Create a thread safe way to call thirdparty global initializers
> ---------------------------------------------------------------
>
> Key: MINIFICPP-877
> URL: https://issues.apache.org/jira/browse/MINIFICPP-877
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Daniel Bakai
> Assignee: Daniel Bakai
> Priority: Major
> Fix For: 0.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
