Joshua Colp dd1b4b38cf devicestate: Don't create topic when change isn't cached. ...

When publishing a device state the change can be marked as being
cachable or not. If it is not cached the change is just published
to all interested and not stored away for later query. This was not
fully taken into account when publishing in stasis. The act of
publishing would create a topic for the device even if it may be
ephemeral.

This change makes it so messages which are not cached won't create
a topic for the device. If a topic does already exist it will be
published to but otherwise the change will only be published to
the device state all topic.

ASTERISK-27591

Change-Id: I18da0e8cbb18e79602e731020c46ba4101e59f0a

2018-07-25 19:20:35 +00:00

..

asterisk

devicestate: Don't create topic when change isn't cached.

2018-07-25 19:20:35 +00:00

solaris-compat

Remove as much trailing whitespace as possible.

2017-12-22 09:14:07 -05:00

asterisk.h

Forward declare 'struct ast_json' in asterisk.h

2017-03-30 22:54:01 -05:00

jitterbuf.h

Remove as much trailing whitespace as possible.

2017-12-22 09:14:07 -05:00