Also ensure that your client is logging the raw data as received from the
socket. Sometimes this will narrows an issue down to a parsing or similar
error in the client.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Fri, Apr 16, 2010 at 9:01 AM, Mark McBride wrote:
>
If you can duplicate this, can you send the exact text, tweet IDs and times
of the runs? Latency on the streaming API should be better than it is in
search (they're both pretty fast), so having the streaming API lag search is
surprising.
---Mark
http://twitter.com/mccv
On Fri, Apr 16, 2010 a
