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
First of all, I´m thinking that maybe we should just go semantic versioning and not make V2 something drastic.
We can gradually add breaking changes without redesigning large portions.
e.g. (take these with a whole hand of salt, just ideas)
Maybe context.Send should be async. so that you can await messages being pushed to a bounded mailbox
Maybe eventstream.Publish should be async. so that you can await the event being consumed by all subscribers.
Maybe context.Parent should be not nullable, and introduce a RootPid, Pid.None which could be used as the parent for top level actors.
Thoughts and suggestions?
The text was updated successfully, but these errors were encountered:
Another thing that would be nice to have, is to expand the decorator context.
currently, you can only decorate the IContext. meaning you cannot intercept whenever an actor reincarnates, handles system messages, and so on.
It would be nice to have those options. e.g. for improved observability
Make it possible to publish to event-stream from a given actor context.
currently we are sending from root context, and if tracing is enabled but not for root context, nothing shows up for this operation.
First of all, I´m thinking that maybe we should just go semantic versioning and not make V2 something drastic.
We can gradually add breaking changes without redesigning large portions.
e.g. (take these with a whole hand of salt, just ideas)
Maybe
context.Send
should be async. so that you can await messages being pushed to a bounded mailboxMaybe
eventstream.Publish
should be async. so that you can await the event being consumed by all subscribers.Maybe
context.Parent
should be not nullable, and introduce a RootPid, Pid.None which could be used as the parent for top level actors.Thoughts and suggestions?
The text was updated successfully, but these errors were encountered: