in some cases, we provide a config with interval set to 'undefined',
which gets happily applied to the config, but gets interpreted as '0'
when actually starting the task, resulting in constant api requests
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this allows to drop setting the default values and ensures that when
interval is updated it actually effects the used update frequency.
Anything which was saved in "me" before, for example me.autoStart, is
still there and gets also updated on a me.setIsStopped(), so there
should be no effects on code using internals.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
since all modern browsers can properly handle multiple
xmlhttprequests, we do not need to serialize them ourselves, but
leave it to the browser
this fixes an issue wehre a canceled request of an updatestore
blocks all other updatestores until refresh
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the store never fires/gets a destroy event, thus it
never stops the load_task and never unqueues itself in case
the store gets destroyed but not explicitely stopped
with overriding the destroy method, this works now as intended
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the alias is to use it in a declarative syntax,
the autostart parameter automatically starts the update
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
