I came to the conclusion that expiration time should really be a backend
property, not a frontend one.
The frontend can always decide to not obey the cache expiration time and
force an update of course. This is in fact happens as part of the midway
refresh strategy or in the pam service where we always make sure to
fetch entries from the source on login.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
I came to the conclusion that expiration time should really be a
backend
property, not a frontend one.
The frontend can always decide to not obey the cache expiration time and
force an update of course. This is in fact happens as part of the midway
refresh strategy or in the pam service where we always make sure to
fetch entries from the source on login.
Simo.
_______________________________________________
sssd-devel mailing list
sssd-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/sssd-devel
Code looks good, but it won't apply on master. Please rebase and I will
test and ack.
- --
Stephen Gallagher
RHCE 804006346421761
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
On Tue, 2009-10-27 at 09:21 -0400, Stephen Gallagher wrote:
> Code looks good, but it won't apply on master. Please rebase and I
> will
> test and ack.
Sent initially to the wrong thread.
_______________________________________________
sssd-devel mailing list
sssd-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/sssd-devel
On 10/27/2009 09:25 AM, Simo Sorce wrote:
> On Tue, 2009-10-27 at 09:21 -0400, Stephen Gallagher wrote:
>> Code looks good, but it won't apply on master. Please rebase and I
>> will
>> test and ack.
> Sent initially to the wrong thread.
> _______________________________________________
> sssd-devel mailing list
> sssd-devel(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/sssd-devel
Ack