Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 91407 invoked by uid 500); 25 Feb 2002 10:58:36 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 91396 invoked from network); 25 Feb 2002 10:58:36 -0000 Mime-Version: 1.0 X-Sender: media@pop3.demon.co.uk Message-Id: In-Reply-To: <3C76D2A8.1070205@anyware-tech.com> References: <3C76D2A8.1070205@anyware-tech.com> Date: Mon, 25 Feb 2002 10:59:22 +0000 To: cocoon-dev@xml.apache.org From: Jeremy Quinn Subject: Re: WriteableSource to write anywhere Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 12:22 am +0100 23/2/02, Sylvain Wallez wrote: >The door is now open to other implementations that will allow us to >write anything anywhere just as Source already allows to read anything >anywhere. Some possible implementations include xmldb (Gianugo ?), SQL >blobs, http/ftp upload, etc. While working on WritableSourceTransformer, I was going to look at making a SourceIOTransformer, that would have two verbs : What do you guys think about this? This is kind of the logical conclusion to the symmetry provided by the new WritableSource interface. It would not completely replace XInclude because it would not be able to do any caching (?). The transformer in the sitemap has no knowledge of what it is going to be asked to do (read or write) or on which resource, this would be for completely dynamic operations I imagine. What do you think? regards Jeremy -- ___________________________________________________________________ Jeremy Quinn Karma Divers webSpace Design HyperMedia Research Centre --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org