[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] XenAPI: Why OpaqueRef instead direct UUID

  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Tue, 22 Mar 2011 19:09:40 +0300
  • Delivery-date: Tue, 22 Mar 2011 09:10:04 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=vV1CO4pIm3tXvWNbQvzEDOaVBOAZHsbAydnPbsn9FGBz6lsw2tADGWViIAReD4FMEF CXyXxnDeUUbbJiXz4zgRcbVq8tFRM+Xba9VEunNyVDh7CMotJoOAAdCzcr0sZz3yWNi+ mFueswGNwOhxw5miq2oktrUenDSxc6K6yya3o=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Good day.

I am using XenAPI for a long time. We have found some performance issues
with XenAPI: the conversion from OpaqueRef to UUID. Each OpaqueRef
should be resolved manually, and this almost doubles request amount.

I got used to them, but I still do not understand why they was
introduced in XenAPI.

Could someone describe me the reason behind OpaqueRefs? Why they are
only valid within a single session? Why they are added in the fist

wBR, George.

xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.