3 ms·
Not only that, but you need to prove you can handle the traffic.
by dev_dull 8y ago
Not only that, but you need to prove you can handle the traffic.
- jaytaylor 8y agoNot in my experience. Why would gnip / twitter care if you can handle it, as long as you pay and abide by the terms of the contract? The burden to fetch the data within the specified window is on the client, it's not a push system. For context: Back in the day, I worked at Klout. We had to pay a crippling monthly sum just to get access to the @mentions stream.
- chrismeller 8y agoAt one point I also read that you had to prove you could handle the traffic. Whether that was a requirement of a technical nature or just to make sure you knew what you were doing so they wouldn't end up holding your hand all the time I'm not sure. They don't specifically say you have to verify anything, but they do dance around being able to handle the volume in a couple of different ways in their streaming guides for us average mortals [1]. It mostly seems to come down to the fact that they are, at least to some degree, buffering on their end to make sure you don't miss anything if there's suddenly a spike that's too large for you to handle or if your connection degrades for a while, etc. It also wouldn't surprise me if it were originally simply a limitation of their internal systems and they couldn't buffer or allow any kind of replay because they were literally just writing everything off to a stream as it came in and didn't have any mechanism for going back and reading from the actual database after the fact. 1: https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/disconnections-explained https://developer.twitter.com/en/docs/tweets/filter-realtime...
- nl 8y agoThis isn't true.