You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/02/07 19:55:34 UTC

[jira] [Commented] (NIFI-329) Provide processor(s) to interact with IRC

    [ https://issues.apache.org/jira/browse/NIFI-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310864#comment-14310864 ] 

Joseph Witt commented on NIFI-329:
----------------------------------

This library looks really well done.  Has a compatible license.  https://github.com/sorcix/sIRC

> Provide processor(s) to interact with IRC
> -----------------------------------------
>
>                 Key: NIFI-329
>                 URL: https://issues.apache.org/jira/browse/NIFI-329
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Examples
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>            Priority: Minor
>             Fix For: 0.1.0
>
>
> - Processor(s) to interact with IRC (sending/receiving)
> One approach: A single processor which both sends and receives data from a given IRC channel.  The user can configure the IRC host, username, password, channel, etc...  The connection then is held open and the processor will produce an output flow file for every message received in the IRC channel which will have as attributes the message content, sender, time, etc..  That same processor can also read flow files from its queue which contain message text in an attribute.  In this manner the processor can support bidirectional interaction with IRC.
> Would then also be interesting to make it really easy for a user to generate a message via the UI as well as easily to consume a message via the UI.  These could be very generic processors/widgets for creation/consumption and good for these sorts of cases.
> There are active IRC channels which are great for demonstration of relatively active datastreams.  Weather updates, Wikipedia updates, etc...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)