And here are the results of the Cocoonian jury (so far):
Carsten John Stephan Piroumian Vadim Sylvain Berin Stefano
a) -1 X
-0
0 X X
+0 X X
+1 X X
b) -1
-0 X
0
+0 X X X
+1 X X X X
c) -1 X
-0
0
+0 X X X X
+1 X X
d) -1 X X X X X
-0 X
0
+0 X
+1
Ok, we have enough -1 on d) so we can skip this solution.
We have two +1 on a), but a -1 from Sylvain
We have four +1 on b) and no -1
We have two +1 on c) and a -1 from Berin
So it seems that we are prefering to remove the SAXConnectors ( a) or b) )
over redesigning the concept ( c) ).
As we have four +1 on b) and no -1, b) is the way to go.
Everyone agreeing with this?
Carsten
> -----Original Message-----
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 27, 2002 12:16 PM
> To: Cocoon-Dev
> Subject: [VOTE]: The future of the SAXConnector
>
>
> 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:
>
> a) Deprecate the SAXConnectors and remove it asap.
> b) Remove it now
> c) Change the concept, so that it is possible to configure
> the used SAXConnector on a map:pipeline base.
> d) Leave it as it is
>
> I'm +1 on b) and -1 on d).
>
> c) seems to be FS, but if there is a real need for SAXConnectors
> we should go for c), so this is a +0 on c).
>
> PS: I like clear votes...
>
> Please make your votes.
>
> Carsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
