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 98901 invoked from network); 19 Sep 2000 14:50:50 -0000 Received: from unknown (HELO mail.supereva.it) (195.110.96.111) by locus.apache.org with SMTP; 19 Sep 2000 14:50:50 -0000 Received: (qmail 24485 invoked from network); 19 Sep 2000 14:48:51 -0000 Received: from unknown (HELO ARES) (151.35.2.244) by mail.supereva.it with SMTP; 19 Sep 2000 14:48:51 -0000 Message-ID: <017e01c02248$d06df270$f4022397@ARES> Reply-To: "Nicola Ken Barozzi" From: "Nicola Ken Barozzi" To: , References: <20000913084212.4627.qmail@web6201.mail.yahoo.com> <000b01c01d7a$6a0daa70$0a022397@ARES> <39C77182.CB87B608@ifrance.com> Subject: Re: [C2]Access control using sitemap Date: Tue, 19 Sep 2000 16:38:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi, Zvi! :-) From: "Zvi" > Hi, Nicola > > Nicola Ken Barozzi wrote: > > [skip] > > > I see two "problems" that he is trying to address: speed(hence caching) > > and inclusion. > > For the speed, I don't think it's an issue, but if you need you can write a > > custom Generator that caches according to you _personal_ needs. > > For the inclusion... it's just a matter of making a transformer that > > gets parameters in input telling the header and footer... not too hard, > > believe me. :-) > > My example is over simplified. I the real life thing, I need to include tens of > other transformed XSP results, most of them unknown on the design time - not > just header and footer :) > > Other "problem" that, solution of Giacomo, use intermediate HTTP requests, to > execute XSPs. I think that is reasonable to have option to execute XSP > programmatically. Then I think I don't understand it well :-( Sorry, could you make it more clear for me with a real-life example. If you wish, of course :-) > There is no "problems" for me, I just think that the whole idea of Cocoon is to > make things simple and easy to use for non-programmers and for fast prototyping > by programmers. My idea is just extrapolation of XSP and sitemap. User can't be > forced, to write Custom Transformer in Java, for such a basic thing, as > inclusion result of another pipeline. Well, I meant "issue", and when I said "you" I intended it in the impersonal way. I think that speaking in terms of site creation and handling (not merely technical possibility) you are right. As fot my idea of using transformers, it makes more sense when the sitemap manager wants to decide to add headers and footers, and it is not your case, right? I don't understand, why is the include transformer not ok for this job? If it is speed, remember that now it uses DOM, but IMO it should/will use SAX, right Donald? :-) nicola_ken Nicola Ken Barozzi - AISA Industries S.p.A http://www.aisaindustries.it/ Via Leonardo da Vinci,2 Ticengo (CR) Italy Research Activity: Politecnico di Milano - Dipartimento di Meccanica Piazza Leonardo da Vinci, n.32 - 20133 Milano (Italy)