[asterisk-commits] mmichelson: branch group/CCSS r213281 - /team/group/CCSS/include/asterisk/ccss.h

[SVN commits to the Asterisk project]

Author: mmichelson
Date: Thu Aug 20 14:33:58 2009
New Revision: 213281

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=213281
Log:
Commit some comments about the app_dial changes I'll
soon be making.


Modified:
    team/group/CCSS/include/asterisk/ccss.h

Modified: team/group/CCSS/include/asterisk/ccss.h
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/CCSS/include/asterisk/ccss.h?view=diff&rev=213281&r1=213280&r2=213281
==============================================================================
--- team/group/CCSS/include/asterisk/ccss.h (original)
+++ team/group/CCSS/include/asterisk/ccss.h Thu Aug 20 14:33:58 2009
@@ -333,6 +333,40 @@
  */
 void ast_set_cc_callback_macro(struct ast_cc_config_params *config, const char * const value);
 
+/* END CONFIGURATION FUNCTIONS */
+
+/* BEGIN TREE STRUCTURES AND APIS FOR APP_DIAL'S USE */
+
+/* The tree app_dial uses must be simple, goddammit. What is needed?
+ * The name of the device/extension being dialed, and what ccss is
+ * relevant for the specific device.
+ *
+ * Think about Dial's operation...When a device is called, it all
+ * happens within the same thread. However, if Dial calls, say, two
+ * Local channels, then there will be two simultaneous threads
+ * which will try to manipulate the same structure. We need a lock.
+ * Of course the other problem is that if this is going to exist
+ * as a datastore on the channel, then dialing local channels should
+ * probably result in their increasing a reference count on the data.
+ */
+
+/* So the gory datastore details will be in app_dial. However, the structure
+ * it makes use of needs to be accessible to the CC core as well. So that
+ * is why this is here and not in app_dial. All right.
+ */
+
+/* All right, so while an actual tree-like structure is necessary in order
+ * to handle all the intricacies of the weighted graph that a monitor uses,
+ * for a simple phone call, that won't be necessary. All that's necessary
+ * is a linked list of devices. Each device contains an indication of who
+ * its "parent" is. This way, A tree may be easily constructed by traversing
+ * the list. We can guarantee that we will generally be going in a top-to-bottom
+ * order.
+ */
+
+/* END TREE STRUCTURES AND API FOR APP_DIAL'S USE */
+
+
 /*!
  * \brief a link that connects two monitors in the weighted graph of 
  * monitor structures.