[asterisk-bugs] [JIRA] (ASTERISK-22038) Create a secondary message router for cached messages

[Matt Jordan (JIRA)]

Matt Jordan created ASTERISK-22038:
--------------------------------------

             Summary: Create a secondary message router for cached messages
                 Key: ASTERISK-22038
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22038
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Core/ManagerInterface
    Affects Versions: 12
            Reporter: Matt Jordan


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}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira