Armin Weisser wrote: > we have a standard magnolia scenario here with an author and a public > instance, each having its own data store. > With this publishing new content from author to public is straight forward. > > We’re just facing the problem that the webapp itself alters content in the > public instance and we’d like to instantly propagate these changes to the > author instance (resp. its data store). > > So we need some sort of automatic reverse publishing process. > > The home grown, naive approach would be to observe changes in the public > instance and send a http request to the author instance. > I also read about using JNDI to enable RMI calls … > Another possible solution would be to handle this on the JCR level. > > Is there a „standard“ way of doing such things with the Magnolia-API?
I don't know what data your web app is changing in your public instances, but for commenting we for instance clustered the forum workspace (which is used to store comments) between all of our instances. Also see http://documentation.magnolia-cms.com/technical-guide/clustering.html for more information on clustering. Nils. ------------------------------------------------------------------------ VPRO www.vpro.nl ------------------------------------------------------------------------ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
