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 83421 invoked from network); 2 Sep 2000 09:51:32 -0000 Received: from anchor-post-31.mail.demon.net (194.217.242.89) by locus.apache.org with SMTP; 2 Sep 2000 09:51:32 -0000 Received: from media.demon.co.uk ([158.152.20.147] helo=[192.168.0.2]) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13V9xU-0009yA-0V for cocoon-dev@xml.apache.org; Sat, 2 Sep 2000 10:51:33 +0100 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: Date: Sat, 2 Sep 2000 10:48:36 +0100 To: Cocoon Dev From: Jeremy Quinn Subject: taking output of XSP Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi All, What with the talk of a new dynamic tag, I'd like to bring up another possible modification to XSP. The FP TagLib has a Tag that directs it's contents to an external file as opposed to the output document. This works fine, request:get-parameter outputs an Element to fp:write. But if someone wants to do this: <request:get-parameter name="title"/> It all becomes rather complicated (or do I misunderstand?). The fp:write Tag would have to take over xspCurrentNode and probably muck around with the Node Stack, both of which I understand are not recommended! Can I safely take over xspCurrentNode etc. or do we need a new mechanism for this? thanks Jeremy -- ___________________________________________________________________ Jeremy Quinn Karma Divers webSpace Design HyperMedia Research Centre