Summary:	ASTERISK-22038: Create a secondary message router for cached messages
Reporter:	Matt Jordan (mjordan)	Labels:
Date Opened:	2013-07-07 20:39:01	Date Closed:	2013-07-23 08:40:01
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/ManagerInterface
Versions:	12	Frequency of Occurrence
Related Issues:	is duplicated by ASTERISK-21977 Stop potential message ordering issues between bridge and channel manager events is related to ASTERISK-22002 Stasis: Split caching from caching topics
Environment:		Attachments:
Description:	Cached messages - all of them, regardless of type - have a single message type and thus have to be handled by the same callback. This is problematic in AMI, where we want to break this up by object type. This is similar to ASTERISK-22002 and may be solved at the same time as it. {noformat} /* BUGBUG - This should really route off of the manager_router, but * can't b/c manager_channels is already routing the * stasis_cache_update_type() messages. Having a separate router can * cause some message ordering issues with bridge and channel messages. */ bridge_state_router = stasis_message_router_create(bridge_topic); if (!bridge_state_router) { return -1; } {noformat}
Comments: