Re: [twitter-dev] twitter streams API related question

2010-09-29 Thread Tom van der Woerdt
To be very simple: Streams = future, REST = past

If it's 8 AM, you should start your application that uses the Stream API
and stop it at around 9:45 AM. Then, for every tweet that comes in, you
would check the time and decide to use it or not.

With the REST API, you execute some requests at 9:45 AM, going back to
9:00 AM. Depending on the amount of tweets sent about AAPL, this may be
a lot of requests. I'd recommend using the Streams API and keep a small
program running to archive (or whatever you want to do with them) the
tweets.

Tom


On 9/29/10 2:36 PM, rakesh wrote:
 Hi -
 
  I would like to download (all) the tweets in the public timeline that
 correspond to a particular keyword (or keywords) from a specific start
 time to end time. Would the streams API help me do this.
 
 For example - all tweets (from all users) that contain the keyword
 'AAPL' between 9 AM and 9:30 AM EST.
 
 
 I realize that the number of requests is rate-limited and hence will
 not result in all tweets - if one gets whitelisted - is it possible ?
 
 Any other way ?
 
 Thanks in advance for your answer(s)
 Rakesh
 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] twitter streams API related question

2010-09-29 Thread M. Edward (Ed) Borasky

Actually, for keyword searches of the past, wouldn't you use Search, not REST?
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

A mathematician is a device for turning coffee into theorems. - Paul Erdos


Quoting Tom van der Woerdt i...@tvdw.eu:


To be very simple: Streams = future, REST = past

If it's 8 AM, you should start your application that uses the Stream API
and stop it at around 9:45 AM. Then, for every tweet that comes in, you
would check the time and decide to use it or not.

With the REST API, you execute some requests at 9:45 AM, going back to
9:00 AM. Depending on the amount of tweets sent about AAPL, this may be
a lot of requests. I'd recommend using the Streams API and keep a small
program running to archive (or whatever you want to do with them) the
tweets.

Tom


On 9/29/10 2:36 PM, rakesh wrote:

Hi -

 I would like to download (all) the tweets in the public timeline that
correspond to a particular keyword (or keywords) from a specific start
time to end time. Would the streams API help me do this.

For example - all tweets (from all users) that contain the keyword
'AAPL' between 9 AM and 9:30 AM EST.


I realize that the number of requests is rate-limited and hence will
not result in all tweets - if one gets whitelisted - is it possible ?

Any other way ?

Thanks in advance for your answer(s)
Rakesh



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:   
http://groups.google.com/group/twitter-development-talk






--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] twitter streams API related question

2010-09-29 Thread Taylor Singletary
With streaming, the present quickly becomes the past. I'd much rather
a developer think pro-actively and capture the tweets they need as
they happen rather than go spelunking through the past as depicted by
the Search API. I think Tom was referring to the Search API when
saying REST of course. Nitpicky nitpicky :).

Taylor

On Wed, Sep 29, 2010 at 8:22 AM, M. Edward (Ed) Borasky
zn...@borasky-research.net wrote:
 Actually, for keyword searches of the past, wouldn't you use Search, not
 REST?
 --
 M. Edward (Ed) Borasky
 http://borasky-research.net http://twitter.com/znmeb

 A mathematician is a device for turning coffee into theorems. - Paul Erdos


 Quoting Tom van der Woerdt i...@tvdw.eu:

 To be very simple: Streams = future, REST = past

 If it's 8 AM, you should start your application that uses the Stream API
 and stop it at around 9:45 AM. Then, for every tweet that comes in, you
 would check the time and decide to use it or not.

 With the REST API, you execute some requests at 9:45 AM, going back to
 9:00 AM. Depending on the amount of tweets sent about AAPL, this may be
 a lot of requests. I'd recommend using the Streams API and keep a small
 program running to archive (or whatever you want to do with them) the
 tweets.

 Tom


 On 9/29/10 2:36 PM, rakesh wrote:

 Hi -

  I would like to download (all) the tweets in the public timeline that
 correspond to a particular keyword (or keywords) from a specific start
 time to end time. Would the streams API help me do this.

 For example - all tweets (from all users) that contain the keyword
 'AAPL' between 9 AM and 9:30 AM EST.


 I realize that the number of requests is rate-limited and hence will
 not result in all tweets - if one gets whitelisted - is it possible ?

 Any other way ?

 Thanks in advance for your answer(s)
 Rakesh


 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk




 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk