Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 60941 invoked from network); 27 Feb 2004 08:02:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Feb 2004 08:02:13 -0000 Received: (qmail 35587 invoked by uid 500); 27 Feb 2004 08:01:47 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 35371 invoked by uid 500); 27 Feb 2004 08:01:46 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 35354 invoked from network); 27 Feb 2004 08:01:45 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 27 Feb 2004 08:01:45 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 858CA19F5EE for ; Fri, 27 Feb 2004 09:01:57 +0100 (CET) Received: from s-und-n.de ([10.10.20.145]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004022708565314-53571 ; Fri, 27 Feb 2004 08:56:53 +0100 Message-ID: <403EFABB.5060408@s-und-n.de> Date: Fri, 27 Feb 2004 09:07:23 +0100 From: Guido Casper User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] Cocoon Input Model References: <403CC415.2020302@nada.kth.se> <403D194A.9020705@nada.kth.se> <403E5B28.8050101@s-und-n.de> <20040226211305.GC19198@maribor.izzy.net> In-Reply-To: <20040226211305.GC19198@maribor.izzy.net> X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 27.02.2004 08:56:53, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 27.02.2004 08:56:54, Serialize complete at 27.02.2004 08:56:54 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Alan wrote: > * Guido Casper [2004-02-26 20:41]: > >>Daniel Fagerstrom wrote: >> >> >>>So a pipeline for input handling could look like: >>> >>>g -> t* -> store -> act -> [select] -> g -> t* -> s. >> >>I'm still not convinced by this symmetry thing :-) >> >>The requirements for inbound data flow seems to be too different from >>those of outbound data flow. >> >>For outbound data flow everything is converted to a string which is >>quite easy and nicely supported by XML's weakly typed nature (IMO one >>major reason for XMLs power and success) and a powerful transformation >>language. >> >>For inbound data flow (as you already mentioned) you need strongly typed >>data which requires parsing, validation and error handling. I do see >>value in putting this data - once grabbed and converted by the forms >>framework - into some sort fo pipeline. What I'm unsure about is if >>these pipelines will be of similar power as weakly typed pipelines. I >>believe Cocoon's pipelines achieve this level of component reusability >>because of its weakly typed (and therefore loosely coupled) nature. >> >>Now IIUC you suggest a pipelining architecture for inbound data flow >>with a DOM-like data model. > > > What do you mean by strongly typed? Are we discussiong form posts > here? Yes, form posts being the use case at hand, but there are other ways input may be provided. Quoting Daniel: >>> Besides using request parameters and "structured" request parameters as user input. XML is used for WebDAV and web service applications, XML are also becoming more common from more advanced user clients. And with new environments like mail, CLI, JMS and possibly more, we will get even more user input formats. <<< Guido > > For some time now, I've wondered how one would post XML to > Cocoon and start out with it in the pipeline. Cocoon would make > short work of REST implementations. > > (Trying to get up to speed.) >