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
At the moment, you can create a Multi from an emitter but you can only configure the back pressure strategy. When using "buffer", it uses the default buffer size. We should allow configuring the buffer size.
Now, the question is what happens if the buffer reaches its full capacity:
should the sender be informed (throwing an exception) - the event is dropped
should the downstream be informed, and so no more event would be received
all the above
The text was updated successfully, but these errors were encountered:
Actually, the async and serialized nature of the emitter does not allow throwing an exception, as it may be thrown from another thread. So, going with 2).
Fortunately, for 1) the caller can check if the amount of request is greater than 0.
At the moment, you can create a Multi from an emitter but you can only configure the back pressure strategy. When using "buffer", it uses the default buffer size. We should allow configuring the buffer size.
Now, the question is what happens if the buffer reaches its full capacity:
The text was updated successfully, but these errors were encountered: