On 02/21/2013 09:54 PM, Dan Callaghan wrote:
Excerpts from Dan Callaghan's message of 2013-02-22 12:51:31
+1000:
> Excerpts from Nick Coghlan's message of 2013-02-22 12:25:03 +1000:
>> I was actually going to ask about that - is there any reason not to
>> have GET counterparts for most of the URLs in the API? It would be
>> nice not to have to go through the main XML-RPC API in order to read
>> back results when testing a harness.
> The recipe XML gives back everything that you can create or modify
> (status, results, logs, ...) so you can just use that.
Actually that's not true, it doesn't give back the complete logs
(obviously) but it does not even give back a *listing* of which logs
exist. There is a separate XML-RPC interface for that.
Which I think is a bug, I
just filed it here:
https://bugzilla.redhat.com/show_bug.cgi?id=915319
So yes, I will definitely add GET for fetching all the stuff back.
On that note, what are people's preferred ways of returning a listing of
resources (e.g. GET /recipe/1234/logs/)? HTML, Atom, JSON array of
hrefs, ...?
_______________________________________________
Beaker-devel mailing list
Beaker-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel