I started playing around with a simple UI to exercise some of the APIs which are not part of the initial client implementation. I dont know if I like it, but it has been a good way to see what writing a real client would be like. If you would like to see it.. check out
http://github.com/bkearney/headpin
It is a ruby app, so you will need to install the following:
rpms: rubygem-rails rubygem-activeresource
gems: haml
It only points to localhost:8080 right now. It currently exposes the following APIS:
GET /certificate POST /certificate GET /owner GET /owner/{id} POST /owner GE /pool GET /product GET /prodcut/{id} GET /rules POST /rules GET /status
-- bk
RUBY!!!!! YAY!!!!!! Very nice. :)
On Mon, Mar 1, 2010 at 8:21 AM, Bryan Kearney bkearney@redhat.com wrote:
I started playing around with a simple UI to exercise some of the APIs which are not part of the initial client implementation. I dont know if I like it, but it has been a good way to see what writing a real client would be like. If you would like to see it.. check out
http://github.com/bkearney/headpin
It is a ruby app, so you will need to install the following:
rpms: rubygem-rails rubygem-activeresource
gems: haml
It only points to localhost:8080 right now. It currently exposes the following APIS:
GET /certificate POST /certificate GET /owner GET /owner/{id} POST /owner GE /pool GET /product GET /prodcut/{id} GET /rules POST /rules GET /status
-- bk
candlepin mailing list candlepin@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/candlepin
On 03/01/2010 09:29 AM, Jesus M. Rodriguez wrote:
RUBY!!!!! YAY!!!!!! Very nice. :)
I actually do not like it as a client.. since I end up having to encode the schema into the domain objects.. and relationships are kinda hockey. But.. it is a good way to learn the REST side of things. I want to do a bit of investigating on Rest styles a bit as we solidify the API.
-- bk
candlepin@lists.fedorahosted.org