Glenn Ricaud

Yes not for binary blobs, but for all the other blobs, we would gain from caching them after their unserialization

Not much. I think this is a quick gain.

I find myself in the same situation. Thousands of ExpirationWatcher goroutines. I think the idea mentioned above is the right direction: one routine taking care of collecting all expired items.

Do in 1.0.1

Bug from graphql-java. Fixed in this commit: https://github.com/graphql-java/graphql-java/commit/e4004d37aa515102b075ebb88c9e11c8a710bb4e#diff-1eca978226cf8b8b21bf9424dca786dd Will update when a release is available. For now we can use toInt as you did

Set session timeout to 36hours for now (No sensitive info and the typical period of use is once every day). Will implement this in next version. I set it back...

Created an issue about email display improvement: #270 We could implement the configuration of email in 1.0.1.

After debug with aro and sts, we found that it is due to invalidation in Enonic XP. I set this issue in IceBox to not forget about it