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 70606 invoked from network); 9 Jan 2001 13:57:28 -0000 Received: from web117.mail.yahoo.com (HELO web117.yahoomail.com) (205.180.60.91) by h31.sny.collab.net with SMTP; 9 Jan 2001 13:57:28 -0000 Received: (qmail 17208 invoked by uid 60001); 9 Jan 2001 13:56:54 -0000 Message-ID: <20010109135654.17207.qmail@web117.yahoomail.com> Received: from [155.35.248.78] by web117.yahoomail.com; Tue, 09 Jan 2001 05:56:54 PST Date: Tue, 9 Jan 2001 05:56:54 -0800 (PST) From: Davanum Srinivas Reply-To: dims@yahoo.com Subject: Re: Status of XMLCompiler To: cocoon-dev@xml.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N FYI, Here's the link to the "XML Compilation" Thread started by Stefano. http://marc.theaimsgroup.com/?t=97178196000002&w=2&r=1 Questions: 1. Shouldn't we be Caching the output of the Serializer and not the intermediate SAX events themselves? (For example the SVG Serializer takes more time to process the request than the Generator's or Transformers in the Chain) 2. Should we place the burden of deciding (whether the result of a request should come from the Cache or generated again from scratch) on the Generator? (This was the case with C1 right?) Thanks, dims --- Paul Russell wrote: > * Carsten Ziegeler (cziegeler@sundn.de) wrote : > > a long time ago, Stefano posted an XMLCompiler to this list. > > Does someone of you know, what the current status of it is? > > I'm not sure, I must admit. > > > Wouldn't it be good to integrate the XMLCompiler/XMLInterpreter > > into C2? (Perhaps for caching?) > > The trouble is that the system was optimised for the reading phase of > the optimisation, which may not be what we want if the sax streams are > being cached on the fly. One option might be to have pluggable > encoder/decoders to enable us to store SAX events in conventional avalon > stream stores. That way, when it's something which is going to be viewed > very often, we could use Stefano's XMLCompiler and XMLInterpreter which > should give us maximal performance when retrieving from the cache, and > when the thing is more balanced, we could use something else? Does that > work for you guys, or do you have other thoughts of how to cache SAX > events? > > > Paul > -- > Paul Russell Email: paul@luminas.co.uk > Technical Director Tel: +44 (0)20 8553 6622 > Luminas Internet Applications Fax: +44 (0)870 28 47489 > This is not an official statement or order. Web: www.luminas.co.uk > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > ===== Davanum Srinivas, JNI-FAQ Manager http://www.jGuru.com/faq/JNI __________________________________________________ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/