felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BJ Hargrave (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-5) Improve event dispatching
Date Wed, 30 Nov 2005 04:38:30 GMT
    [ http://issues.apache.org/jira/browse/FELIX-5?page=comments#action_12358874 ] 

BJ Hargrave commented on FELIX-5:

See the org.eclipse.osgi.framework.eventmgr package in Equinox. It contains a generic event
dispatching mechanism tuned for OSGi framework use. It supports both synchronous and asynchronous
dispatching. It supports efficient snap shots (copy on write) of the listener list for event
dispatching.  It also support multilevel dispatching which is necessary for OSGi lifecycle
support given that bundle register listeners and when a bundle is stopped, all its listeners
must be easily unregistered.

The EventManager is the starting class for using the package and the package has extensive

> Improve event dispatching
> -------------------------
>          Key: FELIX-5
>          URL: http://issues.apache.org/jira/browse/FELIX-5
>      Project: Felix
>         Type: Improvement
>     Reporter: Richard S. Hall
>     Priority: Minor

> The handling of events (e.g., FrameworkEvent, BundleEvent, and ServiceEvent) could be
improved. The current approach is somewhat ugly and is the result of changes to the spec and
understanding of the spec over time.
> Initially, all events were delivered on a separate thread, then it was changed so that
some events were delivered synchronously. The resulting implementation is ugly and difficult
to understand what is going on. It should not be difficult to improve it somehow.
> The original idea was to have a separate, somewhat generic event dispatching queue. It
would be nice if we could still have something like this, but it should be scrapped if it
creates too much bloat and an ugly use case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message