Peter Hunsberger wrote: > On Mon, Dec 22, 2008 at 10:29 AM, Carsten Ziegeler <[email protected]> > wrote: >> Hi, >> >> I just started with looking closer at the pipeline stuff we have for c3 >> atm. My first impression was that there are too many interfaces which >> might confuse users :) As we step away from just a sax based pipeline, I >> fear we really might need all these interfaces :( >> >> The other thing is caching: i guess in many scenarios caching is not >> done on the pipeline or even pipeline component level. So I think we >> should try to make caching more optional - I know that it is optional >> from a feature point but I would like to have the pipeline jar as small >> as possible and move the caching stuff into an optional/additional lib. >> I have no good idea atm how to do this as the pipeline components itself >> need to be aware of caching. But perhaps someone else has? > > Sounds like a perfect opportunity for some Aspect Oriented coding........ ;-) >
:) Yepp, I had the same feeling - but I'm not sure if this makes the thing easier. Especially as I would like to use the stuff in an OSGi environment where it is a little bit harder to use aop (i know, it's possible and people are working on improving it). Carsten -- Carsten Ziegeler [email protected]
