On Thu, Oct 29, 2009 at 15:01, ChadDavis chadmichaelda...@gmail.com wrote:
Sure, I'm familiar with those. But I thought Guo meant that
workspaces should be used for branches, which to me sounds like I, as
a developer, am supposed to use a workspace to create the effect of
branches. This
Hey.
I'm in the design phase of a project. I'm going to use the JCR as my
persistence for a content management system. In our production
environment, we will have several instances of the CMS application
running. Let's say that each of these instances is for a dedicated
client hosted
On Wed, Oct 28, 2009 at 10:05 PM, ChadDavis chadmichaelda...@gmail.com wrote:
independent server. My question is whether it makes sense to use the
same Jackrabbit server for all of the separate instances of our
application. If so, would it make sense to use workspaces for each
connecting
From previous discussion in the maillist, workspace was designed for
use case such as branches. Different workspaces share version history
in a repository.
Branches? Can you give me an example of what a branch is?
Also, I don't understand what the significance of your comment about
version
Branches, revision/version history, etc. are concepts that come from
version control systems (like cvs, svn, etc.) are you familiar with
those?
Basically what Guo Du tried to tell you is that you shouldn't (mustn't
actually) use different workspaces to separate different users
(clients,
