>>> Unfortunately, I can't make all callbacks synchronous or asynchronous
> >>> because this has negative effects on the application in one way or
> >>> another.
> >>
> >> Surely you can make all callbacks async?
> >> You do not h
> On 29 Sep 2019, at 21:41, Eko palypse wrote:
>
> Am Sonntag, 29. September 2019 19:18:32 UTC+2 schrieb Barry Scott:
>>> On 29 Sep 2019, at 14:14, Eko palypse wrote:
>>>
>>> Unfortunately, I can't make all callbacks synchronous or asynchronous
&
Am Sonntag, 29. September 2019 19:18:32 UTC+2 schrieb Barry Scott:
> > On 29 Sep 2019, at 14:14, Eko palypse wrote:
> >
> > Unfortunately, I can't make all callbacks synchronous or asynchronous
> > because this has negative effects on the application in one way or anot
> On 29 Sep 2019, at 14:14, Eko palypse wrote:
>
> Unfortunately, I can't make all callbacks synchronous or asynchronous because
> this has negative effects on the application in one way or another.
Surely you can make all callbacks async?
You do not have to have them wa
though those can be expensive if you use a lot of them. I
> don't know whether async/await unavoidably complicates things.
Thank you very much for your answer.
Unfortunately, I can't make all callbacks synchronous or asynchronous because
this has negative effects on the application in
as the keys and lists of methods being the values.
Notification sent, triggers the list of method to be called. Nothing fancy.
Now, where it gets trickier is that the client should be able to register
synchronous and asynchronous callbacks because some of the actions can't be
done in a synchronous
