[
https://issues.apache.org/jira/browse/CAMEL-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324131#comment-14324131
]
Hendy Irawan commented on CAMEL-8258:
-------------------------------------
Thanks [~ndmar]
Ideally it should be flexible as you said, you might even want to add
additional URI for Twitter component which fits the flexible behavior.
Practically, for me as long as it makes it possible to stream direct messages,
timeline, and mentions, I'm happy. That's waaay better than nothing (i.e. the
polling alternative that we have now).
Note that Twitter itself limits the number of stream connections. So in
practice, a Camel Twitter stream URI only connects for one user and gets all
kinds of messages in that stream, where the processing/filtering is done on the
receiving side, not server side. This filtering work can be from the component
(by configuration) but can also be "freed" (i.e. receive everything) and the
consumer will do filtering by themselves. I myself prefer to get all messages
and then I as consumer will process/filter messages accordingly.
> 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
> 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)
