There are two broad types of Twitter APIs: authenticated and
non-authenticated. The type is mentioned in the API docs.
If your application is lucky enough to need only non-auth APIs then all you
need to do is make HTTP requests and parse the result, in your favourite
language.
Authenticated APIs
no need to chase changes if you take a dependency on a solid library.
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
On Thu, Nov 12, 2009 at 2:37 PM, wrote:
> I was in the same
I was in the same boat as you a few months ago when an associate asked me to develop a twitter appllication and I had never even seen twitter. I was able to use the supplied documentation and produce a working test application with no help. I believe the documentation is the best place to start.
You can use one of the many libraries for most of the more popular
languages(and some for the less popular), or you can create your own library
to communicate to the API.
Ryan
On Thu, Nov 12, 2009 at 3:09 AM, albana wrote:
>
> Hi everybody!
>
> I am about to develop a twitter application and I
