[
https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-890:
------------------------------
Assignee: Jukka Zitting (was: Stefan Guggisberg)
Fix Version/s: 2.2.0
I'll see what I can do about this in the Jackrabbit 2.2 timescale.
Instead of synchronizing things on the SessionImpl instance, I'm thinking of
adding a lower-level SessionState class that encapsulates all per-session state
that needs to be guarded from concurrent access.
> concurrent read-only access to a session
> ----------------------------------------
>
> Key: JCR-890
> URL: https://issues.apache.org/jira/browse/JCR-890
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: David Nuescheler
> Assignee: Jukka Zitting
> Fix For: 2.2.0
>
>
> Even though the JCR specification does not make a statement about Sessions
> shared across a number of threads I think it would be great for many
> applications if we could state that sharing a read-only session is supported
> by Jackrabbit.
> On many occasions in the mailing lists we stated that there should not be an
> issue with sharing a read-only session, however I think it has never been
> thoroughly tested or even specified as a "design goal".
> If we can come to an agreement that this is desirable I think it would be
> great to start including testcases to validate that behaviour and update the
> documentation respectively.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
