-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/24/2010 03:03 PM, Bryan Kearney 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.
>
> 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
I thikn we should keep the consumer.id around. Personally, I
think it'll become a PITA with hibernate if we don't use id.
Also, I see no problem with being able to get to a consumer using
both the dbid and the uuid.
jesus
- --
jesus m. rodriguez | jesusr(a)redhat.com
principal software engineer | irc: zeus
red hat systems management | 919.754.4413 (w)
rhce # 805008586930012 | 919.623.0080 (c)
+---------------------------------------------+
| "Those who cannot remember the past |
| are condemned to repeat it." |
| -- George Santayana |
+---------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAkx0HWUACgkQvJZ57YntiYNMAwCg3WqWzsDNOiCw6u/GwDs1saoJ
sHYAoIZHc/NEi+gy1z52CXo8gFtUkIJX
=ej6I
-----END PGP SIGNATURE-----