[asterisk-commits] russell: branch russell/events r65835 - /team/russell/events/include/asterisk/

asterisk-commits at lists.digium.com asterisk-commits at lists.digium.com
Thu May 24 07:27:57 MST 2007


Author: russell
Date: Thu May 24 09:27:57 2007
New Revision: 65835

URL: http://svn.digium.com/view/asterisk?view=rev&rev=65835
Log:
add a note with my feelings on the way a device state change gets propogated

Modified:
    team/russell/events/include/asterisk/devicestate.h

Modified: team/russell/events/include/asterisk/devicestate.h
URL: http://svn.digium.com/view/asterisk/team/russell/events/include/asterisk/devicestate.h?view=diff&rev=65835&r1=65834&r2=65835
==============================================================================
--- team/russell/events/include/asterisk/devicestate.h (original)
+++ team/russell/events/include/asterisk/devicestate.h Thu May 24 09:27:57 2007
@@ -21,6 +21,15 @@
  *
  * To subscribe to device state changes, use the generic ast_event_subscribe
  * method.  For an example, see apps/app_queue.c.
+ *
+ * \todo Currently, when the state of a device changes, the device state provider
+ * calls one of the functions defined here to queue an object to say that the 
+ * state of a device has changed.  However, this does not include the new state.
+ * Another thread processes these device state change objects and calls the
+ * device state provider's callback to figure out what the new state is.  It
+ * would make a lot more sense for the new state to be included in the original
+ * function call that says the state of a device has changed.  However, it
+ * will take a lot of work to change this.
  *
  * \arg See \ref AstExtState
  */



More information about the asterisk-commits mailing list