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 1889 invoked from network); 20 Apr 2000 17:05:55 -0000 Received: from akira.webslingerz.com (HELO localhost.localdomain) (root@206.66.49.201) by locus.apache.org with SMTP; 20 Apr 2000 17:05:55 -0000 Received: from localhost (balld@localhost) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA07266 for ; Thu, 20 Apr 2000 13:05:53 -0400 X-Authentication-Warning: localhost.localdomain: balld owned process doing -bs Date: Thu, 20 Apr 2000 13:05:53 -0400 (EDT) From: Donald Ball X-Sender: balld@localhost.localdomain To: cocoon-users@xml.apache.org Subject: Re: Sessions & Cookies In-Reply-To: <38FEE277.3ED0041@ivision.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 20 Apr 2000, Sebastien Koechlin I-VISION wrote: > Robin Green a =E9crit : > >=20 > > tom stuart wrote: > >=20 > > > XSL *is* XML. > >=20 > > Yes, but not all XML is interchangeable. - Cocoon doesn't support doing > > everything, everywhere - and for good reason - it's supposed to be abou= t > > content/logic/style separation, while still leaving you some > > flexibility. > >=20 >=20 > As XSL are embled URL stored into an XML, maybe it's possible to > load them using Cocoon, in this case, an XSL document will go > through every Cocoon feature : Producer/Processor/Formatter. >=20 > So XSP, Database access and every interesting feature of cocoon > can work also on a StyleSheet. >=20 > Can it work this way ?=20 If you wrote it, maybe. > Are XSL already loaded by a Producer ? Nope. > Cocoon2 ? Nope. - donald