On 2/19/11 1:49 PM, Paresh Nakhe wrote:
Hi,
From what i understand, there is no concept of rate limiting for
streaming api. Actually it does make sense because if anyone is to use
'statuses/sample' method (say) the limit will soon be crossed. We are
working on something that will heavily use
On going through the documentation in more detail i found this:
- The the track parameter (keywords), and the location parameter (geo) on
the statuses/filter method are rate-limited predicates.
- After the * limitation period* expires, all matching statuses will once
again be delivered, along
On Sat, Feb 19, 2011 at 7:52 AM, Tom van der Woerdt i...@tvdw.eu wrote:
On 2/19/11 1:49 PM, Paresh Nakhe wrote:
Hi,
From what i understand, there is no concept of rate limiting for
streaming api. Actually it does make sense because if anyone is to use
'statuses/sample' method (say) the
On 2/19/11 2:23 PM, Paresh Nakhe wrote:
On going through the documentation in more detail i found this:
- The the track parameter (keywords), and the location parameter (geo)
on the statuses/filter method are rate-limited predicates.
You can't have an infinite number of search terms.
- After
