You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by robert burrell donkin <ro...@blueyonder.co.uk> on 2005/03/20 23:22:29 UTC
[logging] demonstration code
inspired by ceki's examples, i've been working on an extended systematic
analysis of the various classloader cases. there's demonstration code
for them as well as documentation. it's not complete but most of the
substantial cases address by ceki's document are covered. (the
unconventional context classloader cases highlighted by simon are
missing but they need a little more consideration.) i think that
developers should find it interesting and maybe a little educational. it
certainly help me think a lot more clearly about these issues.
my plan is to establish a baseline without fixing bugs so that
theoretical optimum behaviour can be compared to where JCL is now. it
includes configurations which cannot work in theory as well as those
which can.
i'm now trying to work out the best place and packaging for the source.
in some ways, it's not really JCL source and so in some ways, it doesn't
seem to belong in the JCL. on the other hand, i hope that it might be
useful for JCL advanced users and developers.so, there a temptation to
include it (perhaps within a subdirectory).
opinions?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] demonstration code
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sun, 2005-03-20 at 16:54 -0800, Craig McClanahan wrote:
> Sounds like it might fit into a "demo" or "proof of concept" directory
> now, and into the unit test suite later (when all the outstanding
> issues are addressed).
a separate directory sounds like the best approach.
i started playing with the idea that the demonstration code may be able
to be based on unit tests but i've come to the conclusion that it's
cleaner and clearer to use special demonstration code to accompany the
analysis. unit tests can then be targeted at any cases which need
addressing.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] demonstration code
Posted by Craig McClanahan <cr...@gmail.com>.
Sounds like it might fit into a "demo" or "proof of concept" directory
now, and into the unit test suite later (when all the outstanding
issues are addressed).
Craig
On Sun, 20 Mar 2005 22:22:29 +0000, robert burrell donkin
<ro...@blueyonder.co.uk> wrote:
> inspired by ceki's examples, i've been working on an extended systematic
> analysis of the various classloader cases. there's demonstration code
> for them as well as documentation. it's not complete but most of the
> substantial cases address by ceki's document are covered. (the
> unconventional context classloader cases highlighted by simon are
> missing but they need a little more consideration.) i think that
> developers should find it interesting and maybe a little educational. it
> certainly help me think a lot more clearly about these issues.
>
> my plan is to establish a baseline without fixing bugs so that
> theoretical optimum behaviour can be compared to where JCL is now. it
> includes configurations which cannot work in theory as well as those
> which can.
>
> i'm now trying to work out the best place and packaging for the source.
> in some ways, it's not really JCL source and so in some ways, it doesn't
> seem to belong in the JCL. on the other hand, i hope that it might be
> useful for JCL advanced users and developers.so, there a temptation to
> include it (perhaps within a subdirectory).
>
> opinions?
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org