[
https://issues.apache.org/jira/browse/CAMEL-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328744#comment-14328744
]
Nate M commented on CAMEL-8258:
-------------------------------
Ok, so I think "status" streaming, which has been implemented in camel-twitter,
covers timeline data as well as public mentions, while "user" streaming would
cover direct messages. I think this would satisfy the three items you
mentioned, but correct me if I'm wrong here -- I'm not very familiar with
Twitter terminology.
I think that based on the layout of the twitter and twitter4j apis as well as
the camel endpoints, it seems to make more sense to me to structure the
streaming endpoints on the resource-- "streaming/[status/user]"-- and have the
the filter and sample behavior be called via the options (keyword option
already kind of signals for the filtering behavior).
Given this, I think that it would better fit the use case of simply getting a
stream of data and doing filtering later on at the consumer. Instead of having
an endpoint named "streaming/filter" with possibly intention of doing filtering
at that level, it'd be "streaming/user" and "streaming/status". This obviously
runs against the current endpoints, streaming/filter, streaming/sample
endpoints,but they could be kept for backwards compatibility.
Let me know if this makes sense or if I'm off base.
> 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)
