Hi,
You can take some hint from here -
http://hasin.wordpress.com/2009/06/20/collecting-data-from-streaming-api-in-twitter/
Avinash
On Wed, Jul 15, 2009 at 4:43 AM, Joel Strellner j...@twitturly.com wrote:
Why can’t you do this entirely in your code? Why do you need to close
the connection
The Streaming API docs say we should avoid opening new
connections with the same user:pass when that user
already has a connection open. But I'm hoping it is
okay to do this every hour or so ...
If you're only doing this every hour, that's fine by us.
Great, thanks for the
Why can't you do this entirely in your code? Why do you
need to close the connection and reconnect?
My software keeps the local data file open as long as the
connection is open, so the connection must be closed before
the file can be moved or deleted.
Closing a file, moving it, and then
If you're only doing this every hour, that's fine by us.
On Tue, Jul 14, 2009 at 15:58, owkaye owk...@gmail.com wrote:
The Streaming API docs say we should avoid opening new
connections with the same user:pass when that user already
has a connection open. But I'm hoping it is okay to do
Why can't you do this entirely in your code? Why do you need to close the
connection and reconnect?
Closing a file, moving it, and then creating a new file should be able to be
done extremely fast, thus you shouldn't need to close your connection to
Twitter.
Also, if at all possible, JSON
