Juan Hernandez has posted comments on this change. Change subject: aaa: Introducing format to id of User and Group API entities ......................................................................
Patch Set 3: With this schema for identifiers the API consumer can't find the relationship between /domain/<d>/users/<y> and /domain/users/<x>, because the caller can't calculate y from x or x from y in any reasonable way (and it shouldn't, identifiers are expected to be opaque, and users shouldn't do any calculations/parsing with them). We can certainly accept both /users/<x> and /users/<y>, but as it is possible to do x == y there is no reason to confuse the API consumer with two different URIs for the same resource. Callers are familiar with hex-looking identifiers, so using hex encoding is slightly better than URL encoding (and it performs better). -- To view, visit http://gerrit.ovirt.org/26191 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Iaecb5d43945769db82475edde1c7075c1a343c07 Gerrit-PatchSet: 3 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Yair Zaslavsky <yzasl...@redhat.com> Gerrit-Reviewer: Alon Bar-Lev <alo...@redhat.com> Gerrit-Reviewer: Barak Azulay <bazu...@redhat.com> Gerrit-Reviewer: Juan Hernandez <juan.hernan...@redhat.com> Gerrit-Reviewer: automat...@ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
