event system (was: Re: Various)

[Sanjiva Weerawarana <sa...@watson.ibm.com>]

> >1) The event system - how do we expect this to be used?  Is the algorithm
> in
> >EventNotifier.notify() (walk through an enumeration, checking isInstance()
> each
> >time) perhaps a bit inefficient for use in any kind of high-performance
> system?
> >Why is there a persistence system for this stuff?
> >
>
> The event system as it is now is a first pass brainstorm just to get the
> idea thrown into the pot.  Yes, the enumeration is a bit inefficient (any
> ideas for this would be greatly appreciated).  In about another week or so
> I'll revisit this code to improve its efficiency.  Persistence is there to
> allow for various event configuration profiles to be used.  For example,
> you may have a different set of registered listeners for debugging at
> development time versus what you have at deployment time.  The persistence
> mechanism allows you to use multiple profiles depending on the current
> requirements.  Again, just a brainstorm for now.  I committed so I could
> gather feedback on whether or not people would find this type of mechanism
> useful inside Axis.

Can someone please give some intuition as to what the event system is
and what its used for etc. etc.. Also, how does the persistence stuff
relate to the deployment descriptor? In what form is it persisted?

Thnx,

Sanjiva.