On 8/14/02 4:08 PM, "Marc Portier" <[EMAIL PROTECTED]> wrote:
> sorry for the late entry. No problem. We are still talking about this stuff. >> We can assume that everybody runs on the same common version of >> Cocoon, and >> we have a single Cocoon version running on a single Tomcat instance. This >> should satisfy the simple needs, and we can seek solutions for the more >> complex problems as we move along. >> >> The Web ring is the other option which we should consider, and fortunately >> that's something we can start running right away. >> > > in fact it would be really neat to have a webring of such servers in the > end. > each of them could then be running a number of apps, the relevant portion of > the docs, > and refer to each other... > all of them could have same skinning, ... > > I would go for starting the ring, and gradually find out how we can automate > and streamline the different servers in there. > > The newly cvs repository should be driving everything (also the ring-file) > So maybe it makes sense now, when thinking about the organization of the > various apps in there, to reserve space for the mother-of-all-apps-process > (as vagely described) that can be used to easily publish a number of them on > a server. > > I know my thoughts are still a bit weary on this, but my work on the > forrestbot made me think about generalizing the applied pattern to this kind > of stuff... I'll be glad to contribute/co-work on something that could do > this Yes, this is what I was trying to convey too. We need to define this meta application, which is used to create the Web site of the other applications. We need to identify what are the basic needs for such a Web site and its layout. Some skins for this layout would also be good, so that an application's Web site can differentiate its look from others. Regards, -- Ovidiu Predescu <[EMAIL PROTECTED]> http://www.webweavertech.com/ovidiu/weblog/index.html (Weblog) http://www.geocities.com/SiliconValley/Monitor/7464/ (Apache, GNU, Emacs...) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
