</snip> > Well, then please explain how it works inside a pipeline. > The serializer S cannot tell the transformer T to give it > some element, > nor can T ask the generator G to provide data. Following the > SAX api the > generator G tells the transformer T that there is now an XML element > starting (startElement). T may leave it unchanged, modifies it or just > drop it when notifying S with the same API method.
This is the push we are talking about isn't...? seems sensible to me :-) > > > Creating compound pipelines has nothing todo with the > concept of push or pull the way we are used to talk about > push and pull, hence my remark that I would rather not mix up > these terms the way you do > > > > If "we" is the community of Cocoon developers it would be > fine to have a > definition of these terms by hand. I dunno who we are...perhaps i was at least referring to myself :-) > > To get back to Tomas' problem: He wanted to take the word "true" (i.e. > some data) and forward to another page (meaning a browser page -> > redirect, meaning a pipeline -> push). Do you rate my first > post to him > as "helpful" or was in inherently wrong? No, it was inherently helpful and correct IMO!! The only thing which struck me some kind of unlogical was the "think pull in cocoon context", while cocoon is entirely SAX which is push based... > > BTW: Le mie opinione possono cambiare, ma non il fatto che io ho > ragione! ;-) "My opinion can change, but not the fact that I have reason!" It is only for stupid politicians to stay with their opinion, so I totally agree on you!! :-) And certainly, I have many open ends in cocoon, so there is much to learn for me... Ard > > Florian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
