When we can squeeze it in and after we understand various cost issues.
On Fri, Apr 23, 2010 at 5:52 AM, Jeffrey Greenberg
wrote:
> When will we get - aka "not"?
>
> On Monday, April 19, 2010, Mark McBride wrote:
>> To date the streaming API has only supported logical OR in track
>> keywords (ht
When will we get - aka "not"?
On Monday, April 19, 2010, Mark McBride wrote:
> To date the streaming API has only supported logical OR in track
> keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track).
> Today we're happy to announce that we support logical ANDing in
> productio
I love you guys. You did it ... That has increased the Streaming usability
to some 1000 times.
Thanks in million ways,
Alam Sher
On Tue, Apr 20, 2010 at 10:03 AM, M. Edward (Ed) Borasky
wrote:
> On 04/19/2010 04:39 PM, Mark McBride wrote:
> > To date the streaming API has only supported logical
On 04/19/2010 04:39 PM, Mark McBride wrote:
> To date the streaming API has only supported logical OR in track
> keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track).
> Today we're happy to announce that we support logical ANDing in
> production as well.
>
> The track parameter
To date the streaming API has only supported logical OR in track
keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track).
Today we're happy to announce that we support logical ANDing in
production as well.
The track parameter is treated as a series of phrases. Phrases are
separat
