On Thu, Jun 4, 2015 at 10:10 AM Rodrigo Duarte <rodrigodso...@gmail.com> wrote:
> > Also, if we are going to use a delimiter, we need to update the way > projects names are returned in the GET v3/projects API to include the > hierarchy so the user (or client) knows how to request a token using the > project name. > This comment made me think of something (maybe crazy)... I'm hoping that we are not expecting a client to understand how to create the hierarchical representation of the fully qualified project name and instead feed it to them in the JSON responses. If this is the case we can probably control the delimiter on the server side without the client even knowing that there is a delimiter. We could have the first character of this new property actually contain the delimiter used. ".A.B.C" - would mean that "." is the delimiter - vs - "#A#B#C" - would mean that "#" is the delimiter The challenge left is to figure out which delimiter to use. -- David
__________________________________________________________________________ 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
