Rainer Pruy wrote:
Reinhard Poetz schrieb:
Dev at weitling wrote:
But (maybe I have missed some mails) how do you want to make this
Pipeline API? E.g. a SAX-based pipeline is something different than image
data running through several filters. How do you want to prevent the use
of a SAX-events generating component together with an image data
transformer? What about something like it's used in clipboards: each
component offers a list of importable and exportable formats?
See http://marc.info/?l=xml-cocoon-dev&m=120611990603725&w=2 Do the
explanations that this mail answer your question?
They answer a number of questions.
Nevertheless, the question of connection "type" is still open.
Ok, the answer given is "it is up to the components to ensure compatibility".
However, what does this mean practically? Will there be different
"Interfaces" for different type of data to e processed. (SAX events will use
SAX interfaces, image data will use others)
yes, that's the idea (and IIRC it is already implemented this way Corona).
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
