diff options
author | George Joseph <george.joseph@fairview5.com> | 2015-05-27 12:22:39 -0600 |
---|---|---|
committer | Matt Jordan <mjordan@digium.com> | 2015-12-28 13:45:01 -0600 |
commit | 3a1c4885be4eeb3f6c631b0cfb4709442c9464ae (patch) | |
tree | 055f31dd4d56fad74c547104335a30a5259bf6ee /include | |
parent | 5e99ba393ec59a17dd7c810367e456725e377072 (diff) |
endpoint/stasis: Eliminate duplicate events on endpoint status change
When an endpoint is created, its messages are forwarded to both the tech
endpoint topic and the all endpoints topic. This is done so that various
parties interested in endpoint messages can subscribe to just the tech
endpoint and receive all messages associated with that particular technology,
as opposed to subscribing to the all endpoints topic. Unfortunately, when the
tech endpoint is created, it also forwards all of its messages to the all
topic. This results in duplicate messages whenever an endpoint publishes its
messages.
This patch resolves the duplicate message issue by creating a new function
for Stasis caching topics, stasis_cp_sink_create. In most respects, this acts
as a normal caching topic, save that it no longer forwards messages it receives
to the all endpoints topic. This allows it to act as an aggregation "sink",
while preserving the necessary caching behaviour.
ASTERISK-25137 #close
Reported-by: Vitezslav Novy
ASTERISK-25116 #close
Reported-by: George Joseph <george.joseph@fairview5.com>
Tested-by: George Joseph <george.joseph@fairview5.com>
Change-Id: Ie47784adfb973ab0063e59fc18f390d7dd26d17b
Diffstat (limited to 'include')
-rw-r--r-- | include/asterisk/stasis_cache_pattern.h | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/include/asterisk/stasis_cache_pattern.h b/include/asterisk/stasis_cache_pattern.h index 2ea643e19..27761351a 100644 --- a/include/asterisk/stasis_cache_pattern.h +++ b/include/asterisk/stasis_cache_pattern.h @@ -109,6 +109,8 @@ struct stasis_cp_single; /*! * \brief Create the 'one' side of the cache pattern. * + * Create the 'one' and forward to all's topic and topic_cached. + * * Dispose of using stasis_cp_single_unsubscribe(). * * \param all Corresponding all side. @@ -119,6 +121,32 @@ struct stasis_cp_single *stasis_cp_single_create(struct stasis_cp_all *all, const char *name); /*! + * \brief Create the 'one' side of the cache pattern. + * + * Create the 'one' but do not automatically forward. + * + * Dispose of using stasis_cp_single_unsubscribe(). + * + * \param all Corresponding all side. + * \param name Base name for the topics. + * \return One side instance + */ +struct stasis_cp_single *stasis_cp_single_create_only(struct stasis_cp_all *all, + const char *name); + +/*! + * \brief Set up a topic and topic cache forward. + * + * Forward 'from' to 'to'. + * + * \param from Source 'one' side instance. + * \param to Destination 'one' side instance. + * \retval 0 Success + * \retval -1 Failure + */ +int stasis_cp_single_forward(struct stasis_cp_single *from, struct stasis_cp_single *to); + +/*! * \brief Stops caching and forwarding messages. * * \param one One side of the cache pattern. |