[Kimchi-devel] [PATCH] UI enhancement: Request /config/capabilities as soon as possible

[Aline Manera]

On 08/11/2014 03:09 PM, Crístian Viana wrote:
> On 08-08-2014 18:32, Aline Manera wrote:
>> This is not true.
>> The qemu capabilities is also cached on backend. Check 
>> src/kimchi/model/config.py
> 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.
>
> According to the patch's subject and description:
>
> /"Request /config/capabilities as soon as possible//"
> /
> Doesn't the backend already do that by caching the values?
>
> /"/config/capabilities was requested twice for the templates tab: one//
> //request to identify if qemu has spice support and other one to 
> identify//
> //if the qemu has ISO streaming support./"
>
> Shouldn't the second request return instantly with the results cached 
> on the backend by the first request?

All requests are time consuming. Even if there is no logic involved in 
it on backend. Specially for long distant server/client.
Please, check v3.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20140811/c39e582b/attachment.html>