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.
Perhaps consumer.id needs to go away?
We were talking about making owner.key the URL identifier for owners
as well, should that also become owner.id and behave just like
consumer UUIDs?
I do like the idea of the internal/external keys. am I the only one?
-- bk