cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: [VOTE] Remove excalibur instrumentation support from 2.2
Date Sun, 24 Oct 2004 13:45:12 GMT
On Sun, 24 Oct 2004, Carsten Ziegeler wrote:

> The ECM++ is now integrated in 2.2 and it seems that most things
> are running again - even simple XSP pages (haven't tested more yet).
>
> Now, as I mentioned earlier, one idea of ECM++ is to support only those
> interfaces/features that we really need.
>
> One candidate in this category is obviously the instrumentation
> support - the current version of ECM++ doesn't support it.
>
> I think we should remove the support for excalibur instrumentation
> completly from our 2.2 code base, because:
> - only one single class in our whole repository is using instrumentation
>  (the continuation manager)

People havn't got the benefits.

> - instrumentation can be seen as a proprietary solution that noone else is
> using

Not that i know outside the Avalon land, but Avalon-Phoenix did, dunno 
Merlin.

> - when we will have real blocks we will need other instrumentation
> mechanisms anyway as we don't want to depend on excalibur in this case. So
> migrating earlier is better.
>
> Now, don't get me wrong - excalibur instrumentation is really a nice
> project.

It is indeed.

> In the end when we think of real blocks we need another solution anyways -
> this could be JMX or something else, but it's most likely that it won't be

IIRC JMX isn't able to visualize behaviour over time (i.e. concurrent 
useage of a component over time) as graphs.

> excalibur instrumentation. So, imho it's better to move sooner (with 2.2),
> remove the
> instrumentation code, add a different solution and start using that
> throughout
> Cocoon.
> Cocoon is not really affected by the removal, it might only affect users
> that are using the instrumentation for their applications. So these users
> would have to migrate to whatever we build into 2.2 then.
>
> If the result of this vote is to support instrumentation in 2.2, the missing
> code can be added to ECM++ without major problems.
>
> So, please cast your votes on removing the support starting with 2.2:
>
> Carsten
>
> Carsten Ziegeler
> Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.net/weblogs/rael/
>
>

-- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com

Mime
View raw message