[katello-devel] Merged sync status cli/api
Bryan Kearney
bkearney at redhat.com
Mon Aug 29 15:26:50 UTC 2011
On 08/29/2011 11:24 AM, Jason L Connor wrote:
> On Mon, 2011-08-29 at 11:16 -0400, Bryan Kearney wrote:
>> <ACADEMIA>
>>
>> I think the goal is if an action results in a "thing" then you should
>> try and model the thing as a resource. So... you dont
>> do /person/marry
>> you do /marriage
>>
>> </ACADEMIA>
>
> That's an interesting point. And one I'll have to keep in mind for the
> future.
>
>> Having said that, sync is a tough one as the result of a "synced" is
>> kinda odd :)
>> -
>> - bk
>
> Ok, that's the problem I'm having with syncs too. The result of synced
> repo is only an updated state on an existing resource. Or, as in the
> Pulp case, a 202 Accepted, since Pulp doesn't necessarily even do
> anything right away.
>
Yeah.. this is where REST starts to break down. I dont think there is a
correct answer.
-- bk
More information about the katello-devel
mailing list