[asterisk-commits] russell: branch group/gsoc-2009 r183912 - /team/group/gsoc-2009/ideas.txt

[SVN commits to the Asterisk project]

Author: russell
Date: Tue Mar 24 10:24:45 2009
New Revision: 183912

URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=183912
Log:
Remove event cache idea for now

Modified:
    team/group/gsoc-2009/ideas.txt

Modified: team/group/gsoc-2009/ideas.txt
URL: http://svn.digium.com/svn-view/asterisk/team/group/gsoc-2009/ideas.txt?view=diff&rev=183912&r1=183911&r2=183912
==============================================================================
--- team/group/gsoc-2009/ideas.txt (original)
+++ team/group/gsoc-2009/ideas.txt Tue Mar 24 10:24:45 2009
@@ -74,18 +74,7 @@
       as time permits.  Note that this may end up sharing some code with the
       "data get" interface in part a.
 
-   c) Improve the performance of cache handling in the event core.  The event
-      API in Asterisk provides a generic interface for subscribing to and
-      publishing asynchronous events.  It also provides a caching mechanism for
-      events that represent state changes.  So, to find out a state, you can
-      pull it out of the event cache.  For example, the state of devices as used
-      for presence is handled using this mechanism.  The data structures
-      currently used for maintaining the cache are not optimal for performance
-      when the cache gets large.  This project would be to write code to
-      benchmark the performance of the caching mechanism, and then implement a
-      new storage mechanism that is more efficient.
-
-   d) Develop a method for federating Asterisk servers using distributed events
+   c) Develop a method for federating Asterisk servers using distributed events
       with a transport suitable for communication beyond a LAN.  The current
       event infrastructure includes ways to hook in and distribute events
       between servers.  There is a module which implements this, res_ais, but
@@ -93,7 +82,7 @@
       project would be to implement a new event distribution module using a
       protocol such as XMPP, or something else if deemed appropriate.
 
-   e) Implement a method that makes it very easy to add synchronous hooks 
+   d) Implement a method that makes it very easy to add synchronous hooks 
       throughout the code base.  Hooks are arbitrary callbacks within the 
       internals of asterisk where external components can modify asterisk's 
       behavior.  While the dialplan allows applications to control much of the 
@@ -105,7 +94,7 @@
       of a Dial command, or a transfer hook to execute business logic when a 
       SIP REINVITE is received).
 
-   f) Asterisk has a relatively new generic asynchronous event API. While it 
+   e) Asterisk has a relatively new generic asynchronous event API. While it 
       has been implemented in several areas of the code base, one place where 
       it has not been utilized but would make a great fit would be to replace 
       the legacy code used for generating events on the Asterisk Manager