<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 08/11/2014 03:09 PM, Crístian Viana
wrote:<br>
</div>
<blockquote cite="mid:53E906C8.1020309@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 08-08-2014 18:32, Aline Manera wrote:<br>
<blockquote cite="mid:53E541E5.4010709@linux.vnet.ibm.com"
type="cite"> This is not true. <br>
The qemu capabilities is also cached on backend. Check
src/kimchi/model/config.py <br>
</blockquote>
Then why are we caching those values again on the frontend? If the
backend already caches the capabilities information, every call to
"kimchi.getCapabilities" (after the first one) should return
instantly with the cached values. There's no need to cache the
same thing on the backend and then on the frontend.<br>
<br>
According to the patch's subject and description:<br>
<br>
<i>"Request /config/capabilities as soon as possible</i><i>"<br>
</i><br>
Doesn't the backend already do that by caching the values?<br>
<br>
<i>"/config/capabilities was requested twice for the templates
tab: one</i><i><br>
</i><i>request to identify if qemu has spice support and other one
to identify</i><i><br>
</i><i>if the qemu has ISO streaming support.</i>"<br>
<br>
Shouldn't the second request return instantly with the results
cached on the backend by the first request?<br>
</blockquote>
<br>
All requests are time consuming. Even if there is no logic involved
in it on backend. Specially for long distant server/client.<br>
Please, check v3.<br>
<br>
<br>
</body>
</html>