Hi, Am Sonntag, den 20.04.2008, 20:41 +0200 schrieb Julian Reschke: > Tobias Bocanegra wrote: > >>> - in a pure read-only env, start with 1 session for each request or > >>> share the same session among all requests. if you think this could be > >>> a performance problem, implement a static or dynamic session pool. > >>> > >> > ... > >> > >> Hm. How is this going to work in a multi-threaded environment? The JCR > >> spec > >> doesn't give any guarantees... > > that's true, but jackrabbit sessions are thread safe.
Are they really ? > > OK, but then it should be totally clear that this advice only applies to > Jackrabbit. > > Furthermore, do you want to guarantee that future Jackrabbit versions > will behave the same way? Agreed. And on an application level which deals with JCR and uses Jackrabbit just because it is the best implementation available, I would even stick with the JCR spec stating that Sessions need not be thread-safe and thus assume Sessions are NOT thread-safe. Regards Felix
