Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rohit.yadav@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Rohit Yadav <rohit.yadav@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
CC: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 28 Dec 2012 01:53:29 +0530
Subject: Re: [VOTE] Enforcing UUID string in API query
Thread-Topic: [VOTE] Enforcing UUID string in API query
Thread-Index: Ac3kcAmDXpcuRUZ7Ry28gS2RkypoiA==
Message-ID: <895602AE-827D-4DE4-8146-54D865A0EC27@citrix.com>
References: <8E81A714-9DA8-4A67-8421-EB256932D027@citrix.com>
In-Reply-To: <8E81A714-9DA8-4A67-8421-EB256932D027@citrix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Forgot to mention, let's keep the voting period open till 7th Jan 2013 12:0=
0 GMT, i.e. as a lot of people are offline.

On 27-Dec-2012, at 12:11 PM, Rohit Yadav <rohit.yadav@citrix.com> wrote:

> Hi,
>=20
> I'm asking for the community to vote if they want to enforce UUID string =
to be used in parameters while querying an API. This would break any client=
 or script that uses internal ID. AFAIK api response (json or xml, since 3.=
x for sure) always have had UUIDs so if any client/script that uses apis to=
 query entities and base their further operations using ids from the respon=
se(s) should be fine.
>=20
> You may vote by:
> +1 Agree
> 0  No opinion
> -1 Disagree
>=20
> Some context and description:
>=20
> CloudStack uses internal IDs which are long ints and they have a mapping =
between this ID and the external ID or UUID which is a random string of cha=
racters.
> There are DAO classes which provides a mechanism to query a particular ta=
ble(s) and do other operations. There are VO objects which can hold content=
 of a row. In most VO objects a method getId() would return a long int numb=
er which is the internal ID of that entity and they would have a getUuid() =
which returns a unique random string of chars.
>=20
> At present an API can be queried with both ids, for example for param dom=
ainid using uuid in 1 and using id in 2:
>=20
> 1. http://localhost:8080/client?command=3DlistResourceLimits&domainid=3D8=
664e04a-9931-4765-b3456e6888d0fa1d
> 2. http://localhost:8080/client?command=3DlistResourceLimits&domainid=3D1
>=20
> For querying using id, the caller should have idea of the id for that ent=
ity and which is only possible if they have access to CloudStack's database=
. There is no other way of knowing an entity's id, only uuids are sent as i=
ds in the response.
>=20
> Regards.
>=20
>=20