> >>>>From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > >>>> > >>>>Hi, > >>>> > >>>>I refactored the profiling code a little bit, now the > SAXConnectors > >>>>are not used anymore for profiling, making the use of profiling a > >>>>little bit easier. > >>>> > >>>>But I think we should now vote for the future of > SAXConnectors as we > >>>>already have the (incompatible) changes with the handling > of event > >>>>and stream pipelines; so another one in this area doesn't hurt. > >>>> > >>>>So, here we go: > >>>> > >>>>b) Remove it now
+1 SIMPLIFY! > >>>>c) Change the concept, so that it is possible to configure > >>>> the used SAXConnector on a map:pipeline base. -1 Cocoon already has too much going on behind the scenes. The concept of SAXConnectors is dubious at best. Their functions can easily be performed as Transformers, so they only serve to slow things down without providing a compelling reason for existing. > >>>>d) Leave it as it is -1 Kill it! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
