Article Preview
Buy Now
| Print: | |
| PDF: |
Beyond the Limits
Playing with the Technorati API
Analyzing the API and determining the requirements
Issue: 2.1 (August/September 2003)
Author: Didier Barbas
Article Description: No description available.
Article Length (in bytes): 13,278
Starting Page Number: 46
RBD Number: 2123
Resource File(s):
2123.sit Updated: Friday, October 17, 2003 at 12:24 PM
Related Web Link(s):
http://www.sifry.com/alerts/archives/000288.html
Known Limitations: None
Excerpt of article text...
RB 5 brought its slew of new features, albeit with a few bugs along the way. One of the most interesting new features(after the Operator_ keyword, of course!) is the variety of TCPSockets now available to the user. While trying to decide what to select as a new topic for this column, I was playing online with Technorati's Cosmos. It appeared that an API had been made available, and as soon as the announcement was made, a few fellows started issuing wrappers for Python, Java, and so on. I thought it would be a neat trick to do something similar for RB: provide a class or two to transparently manage Cosmos queries. Beyond the obvious benefits of learning how to use HTTPSockets, dictionaries, and a few other neat tricks, I thought that looking into the process of formalizing an API into another language would make interesting reading. Let's see.
Analyzing the API and determining the requirements
We should first look into the API and determine what is needed. The Technorati API has three calls: Cosmos, Bloginfo and Outbound Blogs. This article will deal with Cosmos, the two others being fairly similar in terms of implementation.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
