You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andre (JIRA)" <ji...@apache.org> on 2016/07/12 15:50:20 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=15373114#comment-15373114 ] 

Andre commented on NIFI-329:
----------------------------

https://vic.demuzere.be/projects/sirc/

{code}
Future updates

I have switched to Go for personal projects, and do not spend much time on sIRC anymore. While this wasn’t a problem in the past, the IRCv3 working group has been adding new features to the old IRC protocol. Unless someone else is willing to spend the time, these probably won’t be added to sIRC. I suggest taking a look at the wonderful PircBotX library if you need more support.
{code}

> 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: Andre
>            Priority: Minor
>              Labels: beginner
>
> - 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)