Home

Welcome to the yes-api wiki!

This is an experiment to see how quickly I can throw together a client component library for the Yes.com API. At this point it is approximately 2 hours old, but it has all the necessary moving parts to request and process the JSON responses from the yes.com API. I’ve coded StationCall and StationsCall. This library depends on httpclient 4.0-beta-whatever and some json-lib. This is git, so if you don’t like something, go fork yourself.

Questions:

1. Is there a free Trac hosting provider out there? Or should I just create a free Basecamp account for this? What do people use for Issue tracking on GitHub?
2. Raise your hand if the Affero license offends you on some level. Yeah? Me too, but I selected it as a social experiment. I want to see what the reaction is to the Affero license, and I’m keeping an open mind about the license. I started life as an Apache zealot but (like many) have soften my view of licenses with age.
3. Maven? You hate Maven? I don’t care, I love Maven. I wrote the book on Maven (well, that’s not true, I wrote a large part of the Maven book). It stays, sorry.

TDB:

1. The URL and configuration needs to be abstracted from the Call objects.
2. The library should delegate to HttpClient entirely (or not). I guess users should have the ability to pass this API an implementation of HttpClient that has been configured for all the fanciness that is possible (proxy settings, client certs). There should be two ways to interact with the API, an easy way that takes no config and a custom way that allows for configuration via HttpClient
3. The unit tests should not hit the yes.com service, that’s just bad form.

Completed:

1. DONE Call objects should implement a Call interface and extend an AbstractCall

Yes API is covered under the Affero General Public License version 3.0. Copyright 2008 – Tim O’Brien.

Ack

Thanks for Jeremie Miller, whom I have never met, for directing my attention to this interesting API.