Hi Angela, My understanding of the proposed design was that there would be two parts 1. MK Client - Each repository for a tenant would be using its repositories MK Client stack to communicate with one server which provider the server side implementation for MK layer 2. MK Server
Multiple Repository Instances through there Mk Client stacks would be communicating with single MK Server. This server can be the store for all the different repository instance (tenants). The MK Client would be using some authentication keys based on which access to that section of store would be allowed to it. Chetan Mehrotra On Thu, Mar 22, 2012 at 11:13 PM, Angela Schreiber <anch...@adobe.com>wrote: > hi tom > > i am not talking about multiple workspaces within a single > jcr repository. > > i am talking about multiple jcr repositories within the same > store each of which for example would have a 'default' workspace and > a versionstore and so forth.... > > kind regards > angela > > > On 3/22/12 5:19 PM, Thomas Mueller wrote: > >> Hi, >> >> in other words: the URL use to create the MK instance must not only >>> identify the store and the workspace but also the repository? >>> >> >> I thought we want to keep the data of all workspaces within the same >> physical storage, so use the same MK instance for all workspaces within a >> repository. >> >> >> Regards, >> Thomas >> >>
