Hi Theo, If you want to share the repository between multiple public instances, then there will be only one public instance from author perspective.
Data published by author reaches one subscriber, which shares the repository with other public instances, so they also see the update. However, I see one practical problem here, not sure how that will be handled. When a publishing/activation operation happens, the cache (or only a portion of the cache) gets flushed/cleared, so that the users of the public instance can get fresh content. I think that in this case, this might be a problem, because the cache might get cleared only on one public instance (the one configured as subscriber with the author). Hope this helps. Regards, -Deepak Mittal http://www.XebiaIndia.com On Tue, 2007-05-01 at 10:37 -0500, Theodore Nguyen-Cao wrote: > Hi, > > If I have a single author instance and multiple public instances > subscribing to the author, must the public instances maintain their own > individual content repositories or can they share a repository? > > The reason for multiple public instances is to load balance the CMS on > the web tier. I don't believe there should be a need for them to > maintain their own repositories. > > How does this design impact activation of content? Is there really just > one subscriber but two public instances sharing a repository? > > Thanks in advance, > > Theo > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
