On 27/06/2015 4:29 AM, Chris Dent wrote:
Providing or displaying meaning is why we have other fields or
lookup by reference. An id and title are not the same thing.
The easiest way to follow the rules (that is to create unique,
universal, persistent, portable and meaningless identifiers) is to use
solely a UUID and nothing else when creating resource ids. If you then
need to get additional information on that thing you know you've got a
good id with which to get that information because it is an actual
identifier, by definition.
i take it this applies to namespacing as well?
i'm just curious if there is a reasoning behind the 255 length id limit?
was there a reason UUIDs were not acceptable? or is this a byproduct of
arbitrary, custom ids from the early days?
cheers,
--
gord
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
