ST3: async callbacks are not async

[schlamar]

@jps
I'm no native speaker so I don't know if the term "half-baked" is meant offensive (because it shouldn't). That's the reason for the prefix

I get your point and would agree with the current design if every plugin get its own worker thread and the implications are clearly stated in the docs

[castles_made_of_sand]

@castles_made_of_sand
Thanks for the update. The other async library I'm currently working with is queuing automatically callbacks on the main thread so I missed this. But as you already have pointed out, a fix is really straightforward.

If you are going to criticise something you should at least show you properly understand it.

Your example revealed the depth of your consideration on the topic.

You are really suggesting that for each plugin, for each *_async callback a new thread is spawned automatically ?

[schlamar]

You are really suggesting that for each plugin, for each *_async callback a new thread is spawned automatically ?

No, one thread per plugin, so that one plugin cannot freeze another one.

[castles_made_of_sand]

Just cause you were surprised by the *_async behaviour doesn't mean they don't currently have uses, as is.

No, one thread per plugin, so that one plugin cannot freeze another one.

Just use your futures and threading and get on with it and even while using the *_async, don't do too much work.

Build the abstraction you want.

No, one thread per plugin, so that one plugin cannot freeze another one.

Just throw the callback on a spare thread in a pool type thing?


Gah, I've got too much of a headache to talk more about this now! Sick with a damn fever.