Skip to content
Snippets Groups Projects
Commit 91eba7dc authored by David M. Lee's avatar David M. Lee
Browse files

Stasis documentation updates.

(issue ASTERISK-20887)
(issue ASTERISK-20959)



git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@382724 65c4cc65-6c06-0410-ace0-fbb531ad65f3
parent c0e2ed1f
No related branches found
No related tags found
No related merge requests found
......@@ -35,9 +35,6 @@
* within Asterisk. It is designed to be:
* - Loosely coupled; new message types can be added in seperate modules.
* - Easy to use; publishing and subscribing are straightforward operations.
* - Consistent memory management; all message bus objects are AO2 managed
* objects, using ao2_ref() and ao2_cleanup() to manage the reference
* counting.
*
* There are three main concepts for using the Stasis Message Bus:
* - \ref stasis_message
......@@ -75,11 +72,12 @@
* to the topic is dispatched to all of its subscribers. The topic itself may be
* named, which is useful in debugging.
*
* Topics themselves are reference counted objects, and automagically
* unsubscribe all of their subscribers when they are destroyed. Topics are also
* thread safe, so no worries about publishing/subscribing/unsubscribing to a
* topic concurrently from multiple threads. It's also designed to handle the
* case of unsubscribing from a topic from within the subscription handler.
* Topics themselves are reference counted objects. Since topics are referred to
* by their subscibers, they will not be freed until all of their subscribers
* have unsubscribed. Topics are also thread safe, so no worries about
* publishing/subscribing/unsubscribing to a topic concurrently from multiple
* threads. It's also designed to handle the case of unsubscribing from a topic
* from within the subscription handler.
*
* \par Forwarding
*
......@@ -110,8 +108,10 @@
* removed from the cache). A stasis_cache_clear_create() message must be sent
* to the topic in order to remove entries from the cache.
*
* As with all things Stasis, the \ref stasis_caching_topic is a reference
* counted AO2 object.
* In order to unsubscribe a \ref stasis_caching_topic from the upstream topic,
* call stasis_caching_unsubscribe(). Due to cyclic references, the \ref
* stasis_caching_topic will not be freed until after it has been unsubscribed,
* and all other ao2_ref()'s have been cleaned up.
*
* \par stasis_subscriber
*
......@@ -122,12 +122,10 @@
* threads (this usually isn't important unless you use thread locals or
* something similar).
*
* Since the topic (by necessity) holds a reference to the subscription,
* reference counting alone is insufficient to terminate a subscription. In
* order to stop receiving messages, call stasis_unsubscribe() with your \ref
* stasis_subscription. This will remove the topic's reference to the
* subscription, and allow it to be destroyed when all of the other references
* are cleaned up.
* In order to stop receiving messages, call stasis_unsubscribe() with your \ref
* stasis_subscription. Due to cyclic references, the \ref
* stasis_subscription will not be freed until after it has been unsubscribed,
* and all other ao2_ref()'s have been cleaned up.
*/
#include "asterisk/utils.h"
......
......@@ -42,6 +42,7 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$")
#define NUM_CACHE_BUCKETS 563
#endif
/*! \private */
struct stasis_caching_topic {
struct ao2_container *cache;
struct stasis_topic *topic;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment