From: Eric Day [e...@oddments.org] > The extra cost is this introduces a new type. If we are going with an > authenticated user returning a list of accounts or account/action > tuples, then having another type for resource groups seems > excessive. It seems we only need one mapping layer here, not two.
Sorry, I made that confusing. Resource = Object from our previous discussion. I was using the terminology already adopted by Jorge's group. Resource Group = list of Objects. > I'm not sure if we're agreeing with different terminology or if > there are actually differences. :) What I interpreted on the wiki > didn't seem to line up with how we were talking last Friday on IRC, > but this could be my misunderstanding. Hopefully we're saying the same thing? :) I don't think this is a radically different collection than List-of-Users. -S Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
