From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
...
> I see three solutions:
>
> 1) ignore the proposal (but we must find a way to implement the same
> functionality without hacks!)
> 2) change the Selector interface
> 3) add another pipeline-aware routing sitemap component
>
> Tough decision indeed!
Yup, I have the same feeling.
There is a real need, and it seems that the envisioned solutions don't fit
that cleanly in the global picture yet.
This makes me think of the (apparent?) dichotomy in Cocoon between Event and
Stream pipelines.
Cocoon uses XML internally, but has to interface to a request coming in and
a result to give, all *not* as SAX events.
IMHO it could be possible (but not necessarily desirable) to achieve all
that Cocoon does now with Event+Stream pipelines only using Stream
pipelines, and this is what I've seen many do.
For example, you can check for authorization to see parts of a file in the
event part, with an Action and XSP tags that show-hide parts of content; but
you can also pipe the request in SAX and have a Transformer or even simple
XSL filter the stream based on the stream content itself. Should the Stream
contain only content, or also content metadata that shapes the content
itself? Are there, semantically speaking, different types-levels of content?
It seems that the dual nature of the processing in Cocoon is starting to get
tested by sensible argumentations.
What do you think?
BTW, Java, an Object language, that has primitive types. A hack? I don't
have the answer.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
