Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 36705 invoked from network); 29 Jun 2000 13:29:36 -0000 Received: from hs4.silknet.com (HELO outbound) (206.26.144.4) by locus.apache.org with SMTP; 29 Jun 2000 13:29:36 -0000 Received: from earth.silknet.com ([10.10.10.1]) by outbound with Microsoft SMTPSVC(5.0.2172.1); Thu, 29 Jun 2000 09:29:09 -0400 Received: by earth.silknet.com with Internet Mail Service (5.5.2650.21) id ; Thu, 29 Jun 2000 09:29:09 -0400 Message-ID: <6A2349C5BEF3D211BD690000D11CB35B01319DD5@earth.silknet.com> From: Ed Staub To: "'cocoon-users@xml.apache.org'" Subject: RE: URL Encoding Date: Thu, 29 Jun 2000 09:29:08 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 29 Jun 2000 13:29:09.0759 (UTC) FILETIME=[01B190F0:01BFE1CE] X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Stefano, Just to clarify some of the later mail in this thread... I think your "hack" statement was referring to the notion of using XSLT as a generator. Were you ALSO criticizing the particular detailed technique used in the case at hand ("xsl:value-of...")? If so, can you explain why? In the larger context, this looks like a translation to me, not a generation. Also , I think Ulrich got misquoted more than once... his "looks cool" was in reference to the narrow "xsl:value-of" technique, not to replacing XSLT with XSP. Thanks, -Ed Staub "When you get really good with a hammer, everything looks like a nail." -----Original Message----- From: Stefano Mazzocchi [mailto:stefano@apache.org] Sent: Monday, June 26, 2000 7:17 AM To: cocoon-users@xml.apache.org Subject: Re: URL Encoding Ulrich Mayring wrote: > > Donald Ball wrote: > > > > > > Looks cool, will XSP become obsolete? Some believe so. I don't. XSP are compiled into generators, XSLT with extensions as filters. True, one could implement a dynamic tag in both, but there are cases where it's faster to hardcode the dynamic code at generation time instead of having to parse the generated file and apply the stylesheet. Some XSLT gurus suggested that XSLT can be translated into generators as well, thus removing completely the need for XSP. While I agree with this concept, I don't like how it ends up being. People think at xslt as filtering, using it as a generator is, IMO, a big hack and should be avoided. Also, XSP provide logicsheets and Ricardo is working on a simpler logicsheet language to allow taglibs to be portable. XSLT 1.1 is supposed to have extention portability and this might make everything we do obsolete. But this might take months to be come a reality and we cannot wait for that. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Missed us in Orlando? Make it up with ApacheCON Europe in London! ------------------------- http://ApacheCon.Com --------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org