stasis_cache_pattern: Backport to 13

Somehow stasis_cache_pattern got out of sync between 13 and master
and it was causing duplicate channel message issues in 13 when
related to a specific endpoint. I.E. from statsd,
'endpoints.PJSIP.1174.channels 0|g' was being emitted twice.

Backporting stasis_cache_pattern from master to 13 solved
the issue and running the unit and testsuite tests confirmed
that no new ones were created.

ASTERISK-25317 #close

Change-Id: Ia8707462f62d15eed14541c37f332a7bbbceb548
This commit is contained in:
George Joseph
2016-01-05 10:06:32 -07:00
parent e13719bff1
commit d228b62fd4
3 changed files with 15 additions and 39 deletions

View File

@@ -121,9 +121,12 @@ 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.
* \brief Create a sink in the cache pattern
*
* Create the 'one' but do not automatically forward.
* Create the 'one' but do not automatically forward to the all's topic.
* This is useful when aggregating other topic's messages created with
* \c stasis_cp_single_create in another caching topic without replicating
* those messages in the all's topics.
*
* Dispose of using stasis_cp_single_unsubscribe().
*
@@ -131,21 +134,9 @@ struct stasis_cp_single *stasis_cp_single_create(struct stasis_cp_all *all,
* \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,
struct stasis_cp_single *stasis_cp_sink_create(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.
*