Revision history [back]

The boolean declaration used to be inside of the synchronized block until ZK 7.0.6, and was moved out at that point. This is an intentional change, not a side effect of another change.

Most likely, the previous implementation was causing a dead-lock.

Did you encounter a case desktop cache would fail to expunge (is this a live problem)? or did you see this from review at the moment?

This could be a minor memory leak, potentially. By default, the SessionDesktopCacheProvider will store the desktop cache as a session property. If the cache for a specific user no longer expunge, it will still be destroyed when the session is destroyed.

The boolean declaration used to be inside of the synchronized block until ZK 7.0.6, and was moved out at that point. This is an intentional change, not a side effect of another change.

Most likely, the previous implementation was causing a dead-lock.dead-lock in serialization / deserialization.

Did you encounter a case desktop cache would fail to expunge (is this a live problem)? or did you see this from review at the moment?

This could be a minor memory leak, potentially. By default, the SessionDesktopCacheProvider will store the desktop cache as a session property. If the cache for a specific user no longer expunge, it will still be destroyed when the session is destroyed.