Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 10738 invoked from network); 23 Jun 2000 21:04:15 -0000 Received: from stargazer.dataway.ch (HELO dataway.ch) (qmailr@195.216.64.144) by locus.apache.org with SMTP; 23 Jun 2000 21:04:15 -0000 Received: (qmail 31313 invoked by uid 0); 23 Jun 2000 21:04:01 -0000 Received: from zh2-21.dial.dataway.ch (HELO pwr.ch) (root@195.216.80.149) by stargazer.dataway.ch with SMTP; 23 Jun 2000 21:04:01 -0000 Received: (qmail 7285 invoked from network); 23 Jun 2000 21:03:49 -0000 Received: from donald.pwr.ch (HELO pwr.ch) (giacomo@10.20.30.103) by simba.pwr.ch with SMTP; 23 Jun 2000 21:03:49 -0000 Sender: giacomo Message-ID: <3953D0B1.29A6A69B@pwr.ch> Date: Fri, 23 Jun 2000 23:03:45 +0200 From: Giacomo Pati Organization: PWR Organisation & Entwicklung X-Mailer: Mozilla 4.72 [de] (X11; U; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: [C2] Separating components [was: Sitemap issues to solve] References: <394A74A7.ED5F87CC@apache.org> <012801bfd7ce$64ef4360$8d178cd4@eddie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Ross Burton wrote: > > > 1) Component Model > > ------------------ > > The sitemap has the notion of a general component. I think might be > > dangerous since it could allow cascaded sitemaps to "tweak" the > > component installation and provide security holes. Since I don't think > > sitemaps should deal with such high level components, I suggest we > > remove the > > > > > > > > element from the sitemap and only leave > > > > > > > > > > > > > > as possible sitemap components. > > So we have names like cocoon.xconf for the tags, and > sitemap.xmap for the actual sitemap. Will cocoon.xconf specify a default > sitemap, or will the be the responsibilty of the class creating Cocoon? I've found an older mail concerning the separation of cocoon and sitemap components. Given I'm an ISP offering sitemap functionality to my customer. Would I let them use their own components like parser, store, program-generator and alike (any ISPs on the list)? Given I'm a webmaster of a middle sized company offering sitemap functionality to the development department for intranet solutions. Would I let them use their own components? My personal opinion in both cases is _no_. The reason is that I would like to have the control over the core components used. This doesn't mean I wouldn't be kind to integrate them in the cocoon.xconf in case of the intranet dept. In the ISP case the situation is more complicated. If I integrate custom components is the customer willing to share them with the other sitemap customers? What are your thoughts about that? Giacomo -- PWR GmbH, Organisation & Entwicklung Tel: +41 (0)1 856 2202 Giacomo Pati, CTO/CEO Fax: +41 (0)1 856 2201 Hintereichenstrasse 7 Mailto:Giacomo.Pati@pwr.ch CH-8166 Niederweningen Web: http://www.pwr.ch