cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M Heuer" <>
Subject Re: [Moving on] SAX vs. DOM part II
Date Tue, 25 Jan 2000 08:25:25 GMT
> > if that's the case, then cocoon should
> > in general be able to operate on request and response
> > interfaces rather than on http specific request and response
> > classes. the parts of cocoon which are http specific should
> > only be invoked when handling requests known to be made via
> > http.
>Right now it's tied to HTTP, but I finally see your point (must be the
>fact of being born in a non english-speaking country, or the layer of
>grease and rust that populate my brain).
>Can we think about having a generic (not protocol-specific)
>Request-Response (and Context) object expecially designed for XML
>production? We need to draft those quite soon, because Cocoon 2.0 relies
>100% on that (and I need to have a Beta for XTECH 2000, end of

Woo hoo!

I think we've gotten through.  ;)


Get Your Private, Free Email at

View raw message