Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E831A9DC2 for ; Thu, 5 Jan 2012 05:29:04 +0000 (UTC) Received: (qmail 63566 invoked by uid 500); 5 Jan 2012 05:29:04 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 63511 invoked by uid 500); 5 Jan 2012 05:29:02 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 63320 invoked by uid 99); 5 Jan 2012 05:29:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2012 05:29:00 +0000 X-ASF-Spam-Status: No, hits=-2001.6 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2012 05:28:59 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 4235213910D for ; Thu, 5 Jan 2012 05:28:39 +0000 (UTC) Date: Thu, 5 Jan 2012 05:28:39 +0000 (UTC) From: "Brett Meyer (Commented) (JIRA)" To: issues@camel.apache.org Message-ID: <805756971.8153.1325741319272.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (CAMEL-4017) Continue development of camel-twitter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180191#comment-13180191 ] Brett Meyer commented on CAMEL-4017: ------------------------------------ Willem, I was able to complete the code tonight. All of the "most useful" aspects of the Twitter API are included in our component. Both scheduled polling and direct routes are available for each. What do you need from us to proceed? There's certainly other areas of the API that I plan to include, but I can release those as patches later on. > 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 > > > 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