[
https://issues.apache.org/jira/browse/CAMEL-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168867#comment-15168867
]
Luca Burgazzoli commented on CAMEL-8258:
----------------------------------------
[~ceefour] I've refactored camel-twitter to support more streaming messages in
my own
[fork|https://github.com/lburgazzoli/apache-camel/commit/e86f6f67ee07473523e9889fa9cbe0f79f1c28cc].
The main change are:
- the body type for stream/* is no more of type twitter4j.Status only but it
changes according to the event received
- there is a new header CamelTwitterEventType which carries the event type
(STATUS, DIRECT_MESSAGE, FOLLOW/UNFOLLOW, etc)
- there may be more headers according to the vent received i.e. for FOLLOW
events there are two more headers CamelTwitterUserSource,
CamelTwitterUserTarget with informationabout the parties
The implementation is not yet complete but it would be nice to have some
feedback/review.
> camel-twitter - Support Streaming from User Endpoint including Direct Messages
> ------------------------------------------------------------------------------
>
> Key: CAMEL-8258
> URL: https://issues.apache.org/jira/browse/CAMEL-8258
> Project: Camel
> Issue Type: Improvement
> Components: camel-twitter
> Affects Versions: 2.14.1
> Reporter: Hendy Irawan
> Assignee: Luca Burgazzoli
> Fix For: Future
>
>
> Please support streaming from User endpoint ({{twitter://streaming/filter}}
> Camel URI?) including Direct Messages, which is supported by twitter4j but
> currently ignored by camel-twitter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
