web services - Developing/Testing Twitter apps without slamming the API -
I am currently working on an app that works with Twitter, but while developing / testing ( Especially those parts which are heavily dependent on real Twitter data), I would like to constantly publish APIs or publish junk tweets.
Is there a general strategy for people to take it easily on APIs (separate caching)? I was thinking of rolling my own library which was essentially trying to stop outgoing requests and return fake reactions, but I wanted to make sure that I was not clarified.
I will probably start by joking the specific parts of your API which will require your application. In fact, it can actually force you to come up with a cleaner design for your app, because to make it more or less, you should "do this" instead, instead of "what" in the context of your application Should think about.
For example, if you are using the Twitter Search API, then your application should not be worried at all, whether or not you are using the JSON or Atom format option. The ability to search Twitter and retrieve results using a given query represents the functionality you have to make, so you must have an API copy at that level of intangible. Output format is just an implementation description.
In the context of the API's performance in terms of low-level implementation details, you can make sure that the application expects you to do this. You actually join Twitter for the real that point However, you have already verified that the purpose of the app is to work, so to write REST and exclude the rest and parse the reactions, it is enough Should Idha, so you probably will not end up hitting Twitter with a lot of junk data at that point.
Comments
Post a Comment