On Wed, 2006-11-22 at 02:22 +0200, Jukka Zitting wrote: > > Yes. A JCR Session is not necessarily thread-safe even for read-only > access. So unless we want to introduce a session pool, we need to > block all simultaneous requests within a HTTP session. Note however > that we can (and should) map the login/synchronization filter to just > the JSP pages and servlets that need access to the JCR session - > there's no need to synchronize access to static resources like images, > stylesheets, and javascript libraries.
In a publishing system, images are most often stored in the repository as well. Granted, it's possible to use file system caches for these, but not always. -- Torgeir Veimo <[EMAIL PROTECTED]>
