Does that really solve the problem for you (at least partly)? > -----Original Message----- > From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel- > boun...@pve.proxmox.com] On Behalf Of Stefan Priebe > Sent: Mittwoch, 09. Oktober 2013 09:24 > To: pve-devel@pve.proxmox.com > Subject: [pve-devel] [PATCH] use a calculated interval for updating the > ressources / screens > > --- > www/manager/data/UpdateStore.js | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/www/manager/data/UpdateStore.js > b/www/manager/data/UpdateStore.js index 5d26335..b927930 100644 > --- a/www/manager/data/UpdateStore.js > +++ b/www/manager/data/UpdateStore.js > @@ -19,7 +19,8 @@ Ext.define('PVE.data.UpdateStore', { > var run_load_task = function() { > if (PVE.Utils.authOK()) { > PVE.data.UpdateQueue.queue(me, function(runtime, success) { > - load_task.delay(config.interval, run_load_task); > + var interval = config.interval + runtime*2; > + load_task.delay(interval, run_load_task); > }); > } else { > load_task.delay(200, run_load_task); > -- > 1.7.10.4 > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
