Details
-
Improvement
-
Resolution: Fixed
-
Critical
-
2.1.3
-
None
Description
The usage of the HTTP session for storing the JCR Session and Magnolia HierarchyManager is a major scalability blocker. I think it would be best to use an object pool of the resources needed for anonymous access to the repository (after verification that it is expensive to create those, if not they should just be created on demand and stored in the request or a ThreadLocal or so.). Anonymous access to the public instance should not create any HTTP sessions.
Checklists
Acceptance criteria