Updated imodel - event.streaming #544
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR 1: Updated iModel2
Summary of Changes:
streaming
property onEvent
and a correspondingstream()
method.Processor
logic to distinguish between streaming and non-streaming events:event.streaming
isTrue
, the processor callsevent.stream()
instead ofevent.invoke()
.concurrency_limit
is set.APICalling
to support both normal invocation and streaming within the same class.Why This PR?
streaming = True
) on an event rather than creating a separate streaming event class.invoke()
andstream()
now share a consistent state and error-handling approach.Testing: