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 26558 invoked from network); 21 Aug 2000 04:13:07 -0000 Received: from balld-0.dsl.speakeasy.net (HELO localhost.localdomain) (@216.254.77.75) by locus.apache.org with SMTP; 21 Aug 2000 04:13:07 -0000 Received: by localhost.localdomain (Postfix, from userid 501) id 1A21A4810; Mon, 21 Aug 2000 00:15:59 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id 0BE026081; Mon, 21 Aug 2000 00:15:59 -0400 (EDT) Date: Mon, 21 Aug 2000 00:15:58 -0400 (EDT) From: Donald Ball X-Sender: balld@localhost.localdomain To: Stefano Mazzocchi Cc: cocoon-dev@xml.apache.org, matt@sergeant.org Subject: Re: cache madness In-Reply-To: <39985DBD.E216AA32@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 14 Aug 2000, Stefano Mazzocchi wrote: > Donald Ball wrote: > > > > anyway, for those of you craving a little bit more speed from your XSP > > pages, this little trick'll knock your socks off. i would almost suggest > > adding an optional attribute to the xsp:page element, say, cache="60", > > which would include a variant on this method in the xsp generated classes > > automatically. > > I was thinking of adding caching semantics to XSP for 1.1, input > welcome. welp, no one else has chimed in yet, so here's my two cents. i think you should add an xsp:cache element that would provide a clues to the runtime system. for instance: ... or short, simple, to the point. (note i've copied matt on this since he's got an XSP impl and might have some input here) (would it be worthwhile to create an xsp-dev list strictly for xsp language issues?) - donald