> 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 the
> > 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 con
over the wire, and it’ll create smaller files.
>
>
>
> -Joel
>
>
>
>
>
> *From:* twitter-development-talk@googlegroups.com [mailto:
> twitter-development-t...@googlegroups.com] *On Behalf Of *Alex Payne
> *Sent:* Tuesday, July 14, 2009 4:07 PM
> *To:* twitter-
ter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: Is it okay to close a connection by opening a new
one?
If you're only doing this every hour, that's fine by us.
On Tue, Jul 14, 2009 at 15:58, owkaye wrote:
The Streaming API docs say we should avoid opening new
conne
If you're only doing this every hour, that's fine by us.
On Tue, Jul 14, 2009 at 15:58, owkaye 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 this
> every hou
