Make all calls non-blocking, otherwise it is getting messy

Question

Make all calls non-blocking, otherwise it is getting messy

yrashk opened this issue 14 years ago · comments

Yurii Rashkovskii commented 14 years ago

Also it will be a good time refactor each "command" into a separate class

Yurii Rashkovskii · Answer 1 · Tue Dec 21 2010 00:03:10 GMT+0800 (China Standard Time)

The question is how far should I go with this, like, for example, equality tests, getting global object and so on — should they be non-blocking too?

Yurii Rashkovskii · Answer 2 · Thu Dec 23 2010 18:28:56 GMT+0800 (China Standard Time)

Definitely proplist() and list() as they are affected by getters. By the way I just thought that it might be possible to duplicate every code both blocking and non-blocking with some macro goodness.

Yurii Rashkovskii · Answer 3 · Tue Jan 04 2011 17:15:31 GMT+0800 (China Standard Time)

term_to_js becomes more reliant on a particular VM instance, so pretty much everything should go non-blocking soon.

Yurii Rashkovskii · Answer 4 · Thu Jan 06 2011 15:45:43 GMT+0800 (China Standard Time)

to_string/to_detail_string converted