community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Dreimann (JIRA)" <>
Subject [jira] [Updated] (COMDEV-95) Create a topic-based pub/sub for IResourceChangeListener
Date Tue, 18 Jun 2013 10:43:20 GMT


Joachim Dreimann updated COMDEV-95:

    Summary: Create a topic-based pub/sub for IResourceChangeListener  (was: [GSoC] Create
a topic-based pub/sub for IResourceChangeListener)
> Create a topic-based pub/sub for IResourceChangeListener
> --------------------------------------------------------
>                 Key: COMDEV-95
>                 URL:
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Joachim Dreimann
>              Labels: bloodhound, gsoc2013
> Apache Bloodhound is a software development collaboration tool, including issue tracking,
wiki and repository browsing (see: Bloodhound extends Trac
( with multiple product support, advanced search functionality,
ticket relations, a simpler installer and sleeker user interface. Apache Bloodhound recently
graduated from the Apache Incubator as a stand-alone Apache project. 
> Problem: 
> Resource listeners often will watch events for a limited, well-known set of resource
realms (e.g. ticket + attachment).
> The current dispatching strategy (i.e. match_resource) is mostly ‚Äčcontent based (
). It behaves in O(r * l) order of magnitude. This might lead to a lot of extra (unnecessary)
> Proposed solution: 
> A performance improvement could be to allow listeners to register to dedicated realm
channels (i.e. ‚Äčtopic-based filtering [
]) , thus turning the dispatch algorithm into O(l) , at least when it is a ok to do so ;)
> PS: We shall not loose the current content-based filtering capabilities , so in advance
I advocated using a hybrid strategy .
> Skills needed: 
> Bloodhound and Trac are written in Python, so a moderate dose of Python programing skills
are required. 
> References: 
> Link to the original issue: 
> More GSoC-related tasks for Bloodhound: 
> Guidelines for contributing to Apache Bloodhound: 

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

View raw message