
|
Requirements list (2/2) solution should support notification classes [SC] solution should support notification info [BL] solution should provide the ability to specify the content of notifications to ensure predictability [SC] solution should send sufficient information in a notification so that it can be analyzed independent of the transport mechanism [AB] solution should allow notifications to refer to prior configuration change RPCs solution should not bind subscriptions to a connection [RP] channels for configuration change notifications should share fate with a session that includes a configuration channel [DP] solution should support replay of locally logged notifications [KW] solution should support message chunking capability in cases channels carry mixed RPCs [KW] solution should scale to 30.000-100.000 nodes which may emit notifications [BL] solution should scale to order 30.000-100.000 nodes to send notifications [BL] |