On 08/18/2010 01:07 PM, Wolfgang Sourdeau wrote:
Hi Jason,


You have 2 possibilities. You could keep the suggsted value of 300 and
simply let your user know that their password might take up to 5 mins to
propagate. After all a password change does not happen often.

The other possibility, which you mention, to leave a low cache value is
still acceptable because the web interface tends to perform many small
requests in batch. Meaning that for each batch, the first request will
initialise the cache, which will then speed up the next requests of the
same batch. Thus this still limits the amount of LDAP and database queries.


Cheers,

Thanks Wolfgang,

That's great information and just what I was looking for. I'll leave it set at 30 seconds.

<<attachment: jason_oster.vcf>>

-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to