Kolab 16: Problems after Update

[Bartosiak-Jentys, Chris]

Hi Jeroen,

Thank you so much for taking the time to write this blog post, an 
interesting read and I look forward to reading more of your posts about 
Kolab's architecture (should you have time to write them).

Blog bookmarked and on my reading list :-)

Thanks!

Chris.

On 2016-07-08 14:05, Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2016-07-08 01:28, Bartosiak-Jentys, Chris wrote:
>> Hi Jeroen,
>> 
>> Thank you for the detailed response, its really interesting to learn
>> more about Kolab's architecture and the work that goes into developing
>> it. I just want to say its very much appreciated, thank you to you and
>> all the other contributors.
>> 
>> I had no idea that Kolab cached expensive LDAP searches in SQL, thanks
>> for taking the time to explain this. I admit I had to read over your
>> response a few times to understand it (and still don't fully).
>> Hopefully a better understanding will enable myself and others to
>> submit better bug reports with more relevant logs in future as well as
>> helping others on the list.
>> 
> 
> Given that you were interested, I wrote up a little something about
> the caching related to authentication [1]. I hope it's well-received
> and that I'm going to be able to find the time to write more such
> little posts ;-)
> 
> Kind regards,
> 
> Jeroen van Meeuwen
> 
> [1] 
> https://kanarip.wordpress.com/2016/07/08/kolabs-authentication-cache/