Vadim Gritsenko wrote:
> > > What do others think about this?
>
> The more I read about "pipeline selectors" the less I like them (DOM
> tree building, re-streaming, ...)...
I know, I know, I have the exact same impression myself :/
> However, don't you think that there is some overlap between these
> "sitemap selectors" and recently proposed "multiplexer"?
Hmmm...
> Using DOM
> implementation of it (it is possible to have one), you will be able to
> evaluate XPath expressions and choose one of the several execution paths
> - or pipelines (follow the tail of "RE: is cocoon symmetry a holy
> grail?" for details about this "multiplexer").
>
> What do you think about this?
yeah, that might solve the issue completely with elegance....yeah...
> > > C'mon, without input I won't change anything.
> >
> > In fact I don't think we can change the Selector interface as it is
> > clearly stated what a Selector is and how it works (read: not a
> pipeline
> > component). It doesn't mess with the SAX event in a pipeline (also for
> > backwards compatability).
>
> I agree with Giacomo: let's leave Selectors as they are, messing with
> old and well-known interface does not feel right.
Ok, let's leave them as they are.
Ignoring the issue isn't nice.
So I think the only way is to go with Vadim's proposal and implement
xpath-reacting multiplexers
Vadim, would you mind incorporating this in your proposal and get back
to us with a clear description of the picture?
I honestly admit I don't remember the full details and I might need a
recontextualization.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
