This project has moved and is read-only. For the latest updates, please go here.

LinqtoTwitter and streaming API

Jul 21, 2014 at 3:08 AM
IS LinqtoTwitter the best choice for streaming API ? i heard a bad things about streaming API with LinqtoTwitter and our application completely dependent on realtime twitter data and can't afford to stop for any reason
Jul 22, 2014 at 7:01 AM

There were several bugs in the first version of the new async streaming API, but those are fixed. I have more ideas on new features - one is a stream parser, which you'll see in the Issues list is the most popular request right now. The best thing to do is test it out to see if you like it - feedback is welcome. The downloadable source code has some simple demos.

When starting with Twitter streaming, it's important to read their documentation:

LINQ to Twitter takes care of much of the complexity, but Twitter's guidance is important to know. They discuss rate limits, message types, and how to handle disconnections. e.g. they recommend a back-off strategy to ensure you don't overload their server when trying to re-start a stream. Yes, Twitter does stop your stream at unpredictable times. Therefore, you need to write error handling and reconnect logic to ensure your communications continue. Whether you use LINQ to Twitter or some other approach, doing this research ahead of time will help you design a better system and reduce confusion later on.