felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (FELIX-1960) Fine-grained timeout configuration
Date Mon, 01 Feb 2010 16:32:58 GMT

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

Carsten Ziegeler reassigned FELIX-1960:

    Assignee: Carsten Ziegeler

> 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
> 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.

View raw message