Seesmic API
Matthew and I have been working out some of the core ideas behind the new RESTful API that I am suggesting to Johann that Seesmic adopt. Basically we looked at what the clients and third party developers would need to consume the information that the servers inside of Seesmic generate and came up with a basic set of data. Once we had that data set identified it was really straightforward then to create a REST API that delivers the information in a consistent manner.
Another benefit of "going REST" with the API is that we can take full advantage of the features Merb offers - it supports out-of-the-box REST style routing and does most of the dirty work for you in a sane manner. Once we realized with a quick prototype the advantages (and a few disadvantages for sure) that Merb was offering some of the other ideas I've been working on started to fall into place:
- memcached cloud support
- API proxy to control outside access to the API
- OAuth/OpenID based authentication without having to bother the server
- Scalable either up or out - very nice ;)
- Already in use by large sites
So, now that we have settled on Merb and some of the other ideas, we get to create a working demo and show the team and convince them we are not crazy!