camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Meyer (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4017) Continue development of camel-twitter
Date Wed, 04 Jan 2012 15:25:39 GMT

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

Brett Meyer commented on CAMEL-4017:
------------------------------------

Willem,

Here's a few caveats:

1.) I need to finish exhaustive testing.  I'll complete this tonight.
2.) The plugin encapsulates about 30% of the Twitter API, but most of the "core" areas are
ready.  I'm continuing to add new capabilities.
3.) For the completed capabilities, they're all based on scheduled polling.  I still need
to finish direct route versions that will allow single-use, "get everything" functionality.
4.) I need to put together some documentation on the endpoint URI usage.

It's entirely your call as to when it should be committed to the trunk.  If you'd like to
proceed now, I'm more than happy to release the new work as patches throughout the next few
weeks.
                
> 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

        

Mime
View raw message