Content Comparison

Table of Contents

References

Jira Legacy

	#	Assumption	Notes
1

#

Given the above . This table details

Choose alternative for forwarding

Alternatives
NCMP forwards the CM Data Notification:

as multiple CM Data Notifications on a common external topic with a special header indicating the client-id so the client can filter
as one CM Data Notification on a common external topic with a special header containing ALL client-ids (Array or String with special token separation)
to topic(s) registered by client(s) during Subscription creation

2

Even if clients specify the topic upon subscription creation, can multiple client share the same topic?

Only applies to alternative #3 above

Gliffy

CM Data Notifications Overview
Which are of interest to which Client (subscription ID)

	Cm Handle	Path	A-10	B-52
1	CH-1	/p/c1	Yes	No
2	CH-1	/p/c2	Yes	Yes
3	CH-1	/p/c3	No	Yes
4	CH-4	/p/c2	No	Yes
5	CH-4	/p/c3	No	Yes
6	CH-1	/p/c4	No	No

Alternatives

NCMP (currently) listens to all CM Data Notifications (on an 'internal' topic
NCMP queries its own persistence service to find out which Client(s) are interested in the notifications A-10 and/or B-52
(3 alternatives, see issue #2)