cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject RE: [VOTE] (was: [RT]: Merging Stream And Event Pipeline)
Date Wed, 03 Apr 2002 08:23:25 GMT
On Wed, 3 Apr 2002, Carsten Ziegeler wrote:

>
> Sylvain Wallez wrote:
> >
> > I'd like also we take a formal decision about allowing a Serializer to
> > be a SitemapModelComponent. This comes regularly on the table, and there
> > have been several uses cases showing the need for it, mainly to access
> > the SourceResolver. And I've got a new use case : I'm currently adding
> > source resolving capabilities to SVGSerializer to allow bitmaps to be
> > read using the "blob" SourceFactory. For this, the serializer *needs*
> > the SourceResolver and thus I have a patched version of StreamPipeline
> > that handles this. I also know that other people are using similar hacks
> > (Dims once sent this hack as an aswer to one of your questions).
> >
> > So : do we allow a Serializer to be a SitemapModelComponent ?
> > +1 from me !
> >
> I'm +0 on this. The new source resolver from Avalon I started to integrate
> is available via the ComponentManager, so if a serializer is Composable
> it can use the source resolver then.
> (And I'm waiting for Stefano and Giacomo to come up and give us their -1
> on this :) )

:)

Well, nothing prevents one to implement SitemapModelComponent or
Composable on its own Serializer, so, what should I say. It seems that
people have their cases and needs for it. Ok, go ahead, guys.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message