ilya-stromberg

OK, thanks. Please document it. I didn't find any remarks at the http://vibed.org/docs page. Additional question: what about multithreaded mode support for Vibe.d plugin? For example, I have global variable....

> However, if this variable is a complex type that does any kind of I/O operations or calls yield() Do you mean Vibe.d asynchronous I/O? Do I still need to...

> For default thread local variables you don't have to used any synchronization - they can be safely shared between tasks that run in the same thread Can fiber migrate...

> Currently it's a boolean choice - by default only one thread with an infinite number of fibers is used. We must provide an ability to limit number of fibers....

> This is job of load balancer, not server itself. OK. Assume that all our servers busy (load balancer does great job). What should we do with overload? Also, note...

> The approach used by node-toobusy of measuring event loop latency also sounds interesting and would work exactly like that for vibe.d. Great! Thanks that you read it. @Dicebot, we...

> What is useful though is the built-in ability to report current load to the balancer. OK. If I understand you correctly, we need that server 1) can detect current...

Mozilla's article describes simple way to do this. Sorry if I confused public API and it's usage, but your first answer looks like server doesn't need to calculate load factor...

OK, thanks. Do you want to implement only time-based limit or both time-based and count-based limits?

> If enableWorkerThreads is called (this function will be removed eventually) Do you have any problems with it? Or you just want to change API?