Looks like the API works really well with standard filtering by transforming the queries into OData format. But what about combining events?
Would it be possible to allow the client to combine events, and only receive them if the combination takes place on the server side first?
I assume that using the existing library, you'd have to perform this combination on the client side, which could be heavily inneficient in some scenarios.
Say you have 2 event streams and you want to get a new values once both have produced an output.
Stream 1: --------0--------0-------0--------
Stream 2: 0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-
In the above example, we'd only like to be notified once we have a result for each of them available, which would only happen once the "slower" stream 1 produces values.
If we combine on the client, we need to receive all the unnecessary events from Stream 2 first, and then once an event comes up from Stream 1, join them locally.
Looks like the API works really well with standard filtering by transforming the queries into OData format. But what about combining events?
Would it be possible to allow the client to combine events, and only receive them if the combination takes place on the server side first?
I assume that using the existing library, you'd have to perform this combination on the client side, which could be heavily inneficient in some scenarios.
Say you have 2 event streams and you want to get a new values once both have produced an output.
In the above example, we'd only like to be notified once we have a result for each of them available, which would only happen once the "slower" stream 1 produces values.
If we combine on the client, we need to receive all the unnecessary events from Stream 2 first, and then once an event comes up from Stream 1, join them locally.