On Mon, 10 Feb 2003, Hochsteger Andreas /INFO-MA wrote: > > While I understand your concept, I strongly disagree: SAX provides a > > multidimensional structured data space which is suitable for > > *any* kind > > of data structure. > > That's interesting. > Do you mean namespaces by multidimensional structured data space? > But I doubt that placing binary or non-XML/SAX Text inside of structured > XML-Tags will solve it all ;-) > > > True, maybe not as efficiently as other formats, but removing a fix > > contract between pipeline components will require a pluggable and > > metadata-driven parsing/serializatin stage between each component. > > > > I don't see any value of this compared to the current approach of SAX > > adaptation of external data to the internal model. > > Perhaps you misunderstand something here. > I don't want to change the way, Cocoon handles SAX events right now. > It's more about how we could handle non-SAX data streams a bit better. > > > > I'm sure some of you wanted to be able to build > > applications the same way like > > > Unix shell pipes work. Cocoon was a big step in this > > direction, but it was > > > only applicable for processing XML data. > > > > *only XML* is misleading. *based on SAX* is the sentence. I've never > > perceived this as a limitation, but as a paradigm shift. > > Agreed. > But the real world is not SAX-based and some better way to handle non-SAX > data streams is demanded.
I don't see a demand for non-SAX data streams. I believe that you convert every non XML format into an SAX stream, and at the end into a binary stream, see for example the SWF block. So I think the strength of cocoon comes from using one language/format for comunicating between components. If you need to hide binary code in a SAX stream, you can aways use the base64 format. I agree with you that the Cocoon concept can make more possible than serving HTML page. I think that Cocoon is at the moment a bit too web orientated, IHMO. Stephan Michels. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
