On Wed, 25 Aug 2010, Devan Goodwin wrote:
So lets say we implement a top level link hierarchy, what would this
look like? Something as simple as:
consumers -> "/consumers"
pools -> "/pools"
owners -> "/owners"
entitlements -> "/entitlements"
Do we also need to include info about the supported query parameters?
This is probably more in the realm of a WADL, problem for another day?
I would think that any parameters needed would just be in the href, but
for other optional ones - I really have no idea. I would think that if
we don't have an immediate use case, we should punt on that for now.
Does this list need to get filtered depending on whether or not your
current role has access to those calls? For instance, only a super
admin can list the owners.
Yeah this seems like the right thing to do. IMHO it is poor user design
to present options that are not available.
Cheers,
Devan
On Wed, Aug 25, 2010 at 9:08 AM, Devan Goodwin <dgoodwin(a)rm-rf.ca> wrote:
> On Tue, Aug 24, 2010 at 8:20 PM, Bryan Kearney <bkearney(a)redhat.com> wrote:
>> On 08/24/2010 03:30 PM, Jesus M. Rodriguez wrote:
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 08/24/2010 03:08 PM, Devan Goodwin wrote:
>>>>
>>>> On Tue, Aug 24, 2010 at 4:03 PM, Bryan
Kearney<bkearney(a)redhat.com>
>>>> wrote:
>>>>>
>>>>> On 08/24/2010 09:49 AM, Devan Goodwin wrote:
>>>>>>
>>>>>> On Wed, Aug 18, 2010 at 9:57 AM, Devan
Goodwin<dgoodwin(a)rm-rf.ca>
>>>>>> ???wrote:
>>>>>>>
>>>>>>> Still to do:
>>>>>>> - Possibly serialize ID along with href. (watch out for
consumer.uuid
>>>>>>> and soon, owner.key.)
>>>>>>
>>>>>> Do we want this HATEOAS form of an object to contain
"id" and "href"
>>>>>> both? My concern with the ID is that if you serialize a consumer,
you
>>>>>> have an "id" which is a numeric database ID, but the
"uuid" is the
>>>>>> actual ID we use in all URLs. It seems all kinds of wrong to
return
>>>>>> "id" = "uuid" when the HATEOAS serialization
kicks in, and then "id" =
>>>>>> int when you follow that link.
>>>>>
>>>>> I am not following the issue here.
>>>>
>>>> Basically you'd get HATEOAS form of a consumer:
>>>>
>>>> {'href' = '/consumers/7129-7817-1974', id =
'7129-7817-1974'}
>>>>
>>>> And then when you GET /consumers/7129-7817-1974, your json would now
>>>> contain:
>>>>
>>>> {id = 1, uuid = '7129-7817-1974'}
>>>>
>>>> So the 'id' value would change on you, which is very weird.
>>>
>>> why can't this be:
>>>
>>> {'href' = '/consumers/7129-7817-1974', uuid =
'7129-7817-1974'}
>>>
>>> or
>>>
>>> {'href' = '/consumers/7129-7817-1974', id = 1}
>>>
>>>>
>>
>> I would be fine with this.
>>
>
> I do not see the point in including an ID that's useless to the
> caller, particularly in this 'minimal' serialized form, but if it
> looks ok to you guys it's fine with me. (makes life easier :))
>
>
> --
> Devan Goodwin <dgoodwin(a)rm-rf.ca>
>
http://rm-rf.ca
>
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
_______________________________________________
candlepin mailing list
candlepin(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/candlepin