WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

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

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] XenAPI: Why OpaqueRef instead direct UUID
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=d2pg5KA1GXBis2A7JMDFYlmNaGxor3HgyryJLg9my3s=; b=FDf7KZMu7wnL79MHxm8vGGUEbgwlSI2XEejUJg7VTZC6OSHtdr01uzSWs1UIv0bJnC WXgrAsE+Azouhg8Xod8RG4NG+gSGIV4g6Zf+uMQAK/N7x3cT1mh2e/B5vraKYaLv+zwZ /fjvAZLNuV5daSBS8sRCvqw0K/2I6fs5Tnti4=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
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
place?


---
wBR, George.



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] XenAPI: Why OpaqueRef instead direct UUID, George Shuklin <=