cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan <alan-coc...@engrm.com>
Subject Re: [RT] Cocoon Input Model
Date Thu, 26 Feb 2004 21:13:05 GMT
* Guido Casper <gcasper@s-und-n.de> [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?

    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.)

-- 
Alan / alan@engrm.com / http://engrm.com/
    aim/yim: alanengrm - icq: 228631855 - msn: alanengrm@hotmail.com

Mime
View raw message