jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "harvey waters" <harvey.wat...@googlemail.com>
Subject Re: DM Rule #3: Workspaces are for corresponding nodes.
Date Tue, 10 Jul 2007 08:31:09 GMT
So an 'audit log' would be a good reason to setup a new workspace. We're
thinking here that the audit log is a different perspective (or perhaps
aspect) of the node in the main 'data workspace'.

Is it possible to get a session to write to two workspaces within a
transaction, surely this must be possible as versioning occurs within a
transaction ?

On 7/7/07, David Nuescheler <david.nuescheler@gmail.com> wrote:
> Explanation:
> ---
> JCR introduces the very abstract concept of Workspaces which leaves a
> lot of developers unclear on what to do with them. I would like to
> propose to put your use of workspaces to the following to test.
> If you have a considerable overlap of corresponding nodes (essentially
> the nodes with the same UUID) in multiple workspaces you probably put
> workspaces to good use.
> If there is no overlap of nodes with the same UUID you are probably
> abusing workspaces.
> Workspaces should not be used for grouping or access control reasons,
> even though it may be tempting to put things into a "bucket", I would
> recommend to use a "folder" (node) for your bucket.
> Workspaces are the boundary for references and query.
> Examples:
> ---
> Use workspaces for things like:
> - v1.2 of your project vs. a v1.3 of your project
> - a "development", "qa" and a "published" state of content
> - completely separated applications that should probably run on
> separate repositories to begin with ;)
> Do not use workspaces for things like:
> - user home directories
> - distinct content for different target audiences like public,
> private, local, ...
> - mail-inboxes for different users

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message