Move channel driver Registry manager events to core.

This also shuffles the stasis system topic and related handling.

(closes issue ASTERISK-21488)

Review: https://reviewboard.asterisk.org/r/2631/


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@393804 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Jason Parker
2013-07-08 14:42:57 +00:00
parent 30d379851e
commit 7422581b6d
12 changed files with 359 additions and 67 deletions

View File

@@ -216,27 +216,6 @@ int64_t ast_mark(int, int start1_stop0);
#define ast_mark(a, b) do { } while (0)
#endif /* LOW_MEMORY */
/*!
* \since 12
* \brief A \ref stasis topic which publishes messages regarding system changes
*
* \retval \ref stasis_topic for system level changes
* \retval NULL on error
*/
struct stasis_topic *ast_system_topic(void);
/*!
* \since 12
* \brief A \ref stasis_message_type for network changes
*
* \retval NULL on error
* \retval \ref stasis_message_type for network changes
*
* \note Messages of this type should always be issued on and expected from
* the \ref ast_system_topic \ref stasis topic
*/
struct stasis_message_type *ast_network_change_type(void);
/*! \brief
* Definition of various structures that many asterisk files need,
* but only because they need to know that the type exists.