| Summary: | ASTERISK-22002: Stasis: Split caching from caching topics | ||||
| Reporter: | David M. Lee (dlee) | Labels: | Asterisk12 | ||
| Date Opened: | 2013-07-02 13:20:31 | Date Closed: | 2013-08-01 09:00:01 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Core/Stasis | ||
| Versions: | 12 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | Stasis caching, in its original incarnation, tightly couples the cache and the caching topic. While this was straightforward, it has a big limitation: since there's only a single caching topic per cache, you cannot subscribe to cache updates per-object.
This limitation was made evident in res_stasis.c, where the code subscribes to the channel caching topic, but then filters out received messages by channel id. If we were to split caching from the caching topic, then res_stasis can subscribe to individual channel caching topics, which is generally more useful. This cleans up res_stasis.c, and is generally a good splitting of responsibilities. | ||||
| Comments: | |||||