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
It would seem that if anything should be "async" on the CommandProcessor it should be Call.
For systems with a Transport there is a lot of "waiting".
Especially as there are several .GetAwaiter().GetResult()s in the current impl.
It appears that the necessary async versions of the internals are available.
Doing this myself would require quite a lot of copy/paste and supplying dependencies etc.
(for context... This is a stepping stone to move a legacy system to a happier place)
So, the question...
Am I over thinking this?
Is this just not a focus for Brighter (it's not intended as a generic bus with rpc etc)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It would seem that if anything should be "async" on the CommandProcessor it should be
Call
.For systems with a Transport there is a lot of "waiting".
Especially as there are several
.GetAwaiter().GetResult()
s in the current impl.It appears that the necessary async versions of the internals are available.
Doing this myself would require quite a lot of copy/paste and supplying dependencies etc.
(for context... This is a stepping stone to move a legacy system to a happier place)
So, the question...
Am I over thinking this?
Is this just not a focus for Brighter (it's not intended as a generic bus with rpc etc)
Beta Was this translation helpful? Give feedback.
All reactions