Hi, On Wed, Feb 19, 2014 at 10:09 AM, Jukka Zitting <[email protected]> wrote: > ...We won't support workspaces in the full JCR sense (shared jcr:system, > cross-workspace operations, etc.). However, we do allow a repository > to have more than one workspace, each workspace being it's own > "mini-repository" with it's own user accounts, node types, version > histories, etc...
Sounds good to me. Would that also allow for tuning various parts of the content tree according to their usage, like for example saying that /tmp and /var have no indexing, no versioning and no observation? I haven't checked if other features of Oak allow that, but that would be useful in large content repositories. Each partition having its own user accounts is a bit worrying though, won't that be an operations/admin problem? If you compare that with unix filesystem partitions, all partitions share a common security layer that's implemented on top of them. -Bertrand
