[ 
https://issues.apache.org/jira/browse/FELIX-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved FELIX-1960.
-------------------------------------

    Resolution: Fixed

I'Ve added a new configuration property which can contain a string array (in 
the case of a configuration object) and a list of strings separated by comma 
(for framework property).
If a value ends with a dot, all handlers in exactly this package are directly 
called  (e.g. org.apache.felix.eventhandlers. )
If a value ends with a star all handlers in this package or any sub package are 
directly called (e.g. org.apache.felix* )
No dot or no star: exact class name (e.g. 
org.apache.felix.eventhandlers.TrustMeHandler )

> Fine-grained timeout configuration
> ----------------------------------
>
>                 Key: FELIX-1960
>                 URL: https://issues.apache.org/jira/browse/FELIX-1960
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin 1.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: eventadmin-1.2.0
>
>
> The timeout setting for event delivery is currentl a global setting - event 
> listeners should (recommended by the spec as well) start an async thread if 
> they need some time to process the event.
> With the timeout setting in place, this creates two threads for each event 
> delivery: one for the timeout handling and one for the event processing.
> I think it would be nice, if one could optimize this behaviour by configuring 
> the event admin to directly call specific event listeners and don't check the 
> timeout. An administrator could add well-known event listeners to this 
> configuration. This would reduce the server load for well-behaving event 
> listeners.
> I could imagine something like 
> ignore.timeout.for=org.apache.sling.jcr.*,my.special.EventListener  (with a 
> better name for the config property) - so you can either add package prefixes 
> or specific classes to the configuration.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to