----- Original Message -----
From: "Sven Kieske" <svenkieske(a)gmail.com>
Sent: Friday, January 9, 2015 2:05:30 PM
Subject: Re: [ovirt-devel] [ENGINE] Question about refresh parameter
-----BEGIN PGP SIGNED MESSAGE-----
On 09.01.2015 14:00, Alexander Wels wrote:
> If you can find all locations that assume the value is true and
> don't explicitly set it, and you change them to explicitly set
> them, then there should be no problem. Otherwise things that are
> expected to refresh the session will no longer do so, which will
> result in some unpredictable behavior.
I smell breakage here.
> On Friday, January 09, 2015 04:52:15 AM Yair Zaslavsky wrote:
>> Hi all, Can anyone think of an issue with changing the default
>> value of the refresh parameter to false for the query mentioned
>> at $Subject?
You should at least provide a reason why you want to change it, imho.
The motivation behind this is that HTTP GET /ovirt-engine/api
should not refresh Engine user session, i.e. such request
should not prevent the Engine user session from expiring.
/ovirt-engine/api is not a resource/collection on its own,
it's an entry point to REST interface that lists top-level
resource collections (DCs, VMs, etc.) plus some additional
REST metadata, so it can be considered as "meta resource";
any activity on it should not be considered as activity on
"real" resources. Well, this is my understanding.
Anyway, as far as I understand, the "refresh" flag on queries
was designed to support use case when GUI (client) polls the
Engine for data but still allows user to be auto-logged-out
of GUI due to user's inactivity.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
Devel mailing list