Hi all, Sling's support for accessing JCR repositories always included a session pool. This session pool dates back some years before Day contributed Sling to the ASF at a time, where Jackrabbit and, more importantly then, Day's CRX were early release stuff and Session setup was dead slow.
In the meantime, Jackrabbit went through a number of release cycles and Session setup time improved a lot. In fact using the Session pool is even slower than not using it ! So, I propose we drop the Session pool from the jcr/base module altogether and just keep the (optional) functionality to limit the number of simultaneous sessions per user. WDYT ? Regards Felix PS: Regarding timing: I did a stupid test of logging in and out 1000 Sessions (at most 5 Sessions concurrently open). Running the test with a session pool of 10 sessions took roughly 3 times as long as running with the pool disabled !
