Closed babijo closed 10 years ago
This is a new thing. Maybe something's changed in google api.
This connect to passive db is normal. Because Streaming db is an independent db, so each time I refresh the streaming result, it gives a message that I've been connected. But the statusCode bug is a new thing for me.
2 possibilities:
Fine. This is a silly conception of "TWIT" node module which can not handle a bad response error (well, no statusCode may be too bad for it). I've added something to handle it and now the streaming is still running since 1 hour already.
Fixed. Theoriquement...
why the collection module disconnects itself after some time?