Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of douglass.doug@gmail.com
 designates 64.233.162.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=awd/vZ05lfO6duobmzTDcVd5QMrWU0RQQrxVPRt27qKV6P6txuzLECG0GXpYzuXDQWqBoYswiPSNpIH9BpzCZR9F77+BVeBpUiNL+8mhGXAOHiD9y2A69jeSw4nBl8Y+UbXUU/C/dioUt584mXs4Bc4G2XpQXMcHwjVefaTqdj8=
Message-ID: <3a9670a0606300742s297d148ey5decd0b58cb26f6@mail.gmail.com>
Date: Fri, 30 Jun 2006 08:42:11 -0600
From: "Doug Douglass" <douglass.doug@gmail.com>
To: users@jackrabbit.apache.org, tobias.bocanegra@day.com
Subject: Re: understanding of Workspace
In-Reply-To: <8be731880606290305k3a4952acu23ab8ed6344e929f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3441_13804536.1151678531845"
References: <3a9670a0606281500m64b74580ieff1e0cc78e9e85f@mail.gmail.com>
	 <8be731880606290305k3a4952acu23ab8ed6344e929f@mail.gmail.com>

------=_Part_3441_13804536.1151678531845
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Toby, definitely helps.

On 6/29/06, Tobias Bocanegra <tobias.bocanegra@day.com> wrote:
>
> hi doug,
> i think it depends on how you want to control which documents your
> read-only app can see. i assume you want to 'publish' the documents
> from you admin-application to the search-application. you can either
> flag the published documents, and include this flag in all your
> queries, or you can clone them into another workspace. imo, the 2
> workspace-approach is the leanest, but uses of course twice as much
> persistence-resources.
>
> regards, toby
>
> On 6/29/06, Doug Douglass <douglass.doug@gmail.com> wrote:
> > I'm seeking a little clarity understanding how Workspaces fit into
> overall
> > JCR picture.
> >
> > FYI, I've got a lot of Documentum baggage that I think is clouding my
> mind
> > -- don't hold it against me ;)
> >
> > Specifically, we're building a digital asset mgmt system based on
> > JCR/Jackrabbit. Our current plan is a model 2/container-shared
> deployment.
> > We have two clients applications: read-only servlet-based search and
> > retrieval; and a read-write admin webapp with only a handful of users.
> In
> > our first delivery, the search servlet will limit access based on the
> > application making the request. Eventually we'll use ACLs to restrict
> based
> > on the actual remote user's roles (all of that centrally managed via
> LDAP
> > and a single user/access model across several containers/hosts; third
> party
> > application access will be considered later).
> >
> > So, how do Workspaces fit into this:
> >
> >   * do we need more than one WS?
> >
> >   * if more than one, is it one WS for read-only and one for read-write?
> >
> >   * or should we expect one WS for each application (admin webapp, and
> one
> > each for the remote applications that search and retrieve)
> >
> >
> > I searched the wiki and read the API javadocs, but nothing provided
> enough
> > depth.
> >
> > Pointers to any materials are very much appreciated.
> >
> > TIA,
> > Doug
> >
> >
>
>
> --
> -----------------------------------------< tobias.bocanegra@day.com >---
> Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
> T +41 61 226 98 98, F +41 61 226 98 97
> -----------------------------------------------< http://www.day.com >---
>

------=_Part_3441_13804536.1151678531845--