[
https://issues.apache.org/jira/browse/NIFI-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andre resolved NIFI-1226.
-------------------------
Resolution: Fixed
A pattern (created as part of ListenRELP has been implemented). Most similar
processors should be able to follow a similar approach
> Implement interprocessor pub/sub API
> ------------------------------------
>
> Key: NIFI-1226
> URL: https://issues.apache.org/jira/browse/NIFI-1226
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Andre
>
> As I try to get my head around NIFI-856 I've noticed that coding "Listeners"
> for NiFi is quite complex endevour.
> ListenHTTP, ListenUDP and ListenSyslog all seem to have a need to tackle the
> transmission of messages between the Listener "daemon" and the onTrigger
> method. (e.g. syslogEvents within ListenSyslog).
> Shouldn't the framework contain something that makes it easier to write this
> sort of processor instead of having to recreate them?
> I believe it may be fair to say nearly every Listen processors will:
> 1. Bind to a socket;
> 2. Receive messages;
> 3. Read messages;
> 4. Add them flowfile;
> 5. Acknowledge receipt;
> Where 4 and 5 are usually applicable to some protocols (like Logstash,
> RELP, RLTP, etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
