Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 5 Jan 2012 21:40:39 +0000 (UTC)
From: "Brett Meyer (Reopened) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <1168695833.11677.1325799639640.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (CAMEL-4017) Continue development of
 camel-twitter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened CAMEL-4017:
--------------------------------

    
> Continue development of camel-twitter
> -------------------------------------
>
>                 Key: CAMEL-4017
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4017
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Brett Meyer
>              Labels: twitter
>             Fix For: Future
>
>         Attachments: svn-camel-twitter-outgoing-changes.jpg
>
>
> CAMEL-1520 resulted in the beginnings of camel-twitter, a component for consuming and publishing through the Twitter API.  The issue is marked as WON'T fix, as the authors decide to start investigating a more generalized social media component.
> The src is currently sitting in Bruno's https://github.com/brunoborges/camel-twitter.  I propose continuing development, hopefully adding it to the camel-extra repository.
> In my opinion, keeping this separate, rather than adding to a generalized social media plugin, would be important.  Twitter usage, and the context the component would be used, can be drastically different.
> I would be more than willing to take ownership of the effort and begin to contribute.  There's several areas of the Twitter API that we use that would be extremely helpful to add as a Camel endpoint (streaming connections, etc.).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira