You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**ST 0.2:**Discover supported and available streams, then select available streams
Query:
What are the expected streams to be supported or made available for this usecase? Should we have object specific streams made available to end-user? Is it necessary or can there be a single stream to publish all kinds of events?
The text was updated successfully, but these errors were encountered:
Thanks for the question, @kgkishore, @roshan-joyce-fujitsu has identified text in TR-548 that explains the intention. The approach to stream combinations has not been restricted. The assumption is that a client will identify which entities arrive through which streams and then will combine the flows appropriately to build the necessary structures in its repository. Streaming allows for trees to be build (as per YANG) but also allows a flatter more meshy structure to be built.
On a related point, clearly, as with any notification/streaming solution, there is an eventual consistency consideration. Information may be received where that information includes a reference to something that is not yet known. We can go into this in more detail on a call if relevant.
**ST 0.2:**Discover supported and available streams, then select available streams
Query:
What are the expected streams to be supported or made available for this usecase? Should we have object specific streams made available to end-user? Is it necessary or can there be a single stream to publish all kinds of events?
The text was updated successfully, but these errors were encountered: